headers
Michael Berg (JIRA | 1 Dec 2011 14:53

[jira] Commented: (JBEHAVE-207) Exclude SCM patterns from ScenarioClassNameFinder


    [
https://jira.codehaus.org/browse/JBEHAVE-207?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=284684#comment-284684
] 

Michael Berg commented on JBEHAVE-207:
--------------------------------------

Using maven 3.0.3 and jbehave-maven-plugin 3.5.3, I am able to reproduce the problem above. I am using the
maven command line client, not the embedded eclipse maven.

The problem seems to manifest itself only with the maven "site" goal. In this case the configuration
section appears to be more or less inherited from the maven-surefire-plugin configuration?? This is
true at least for the includes and excludes. I have no idea how this can be, but it is pretty easy to verify.

An "mvn test" runs fine, with configuration data injected as expected.

I think this issue needs to be reopened and looked at, there is definitely something funny going on here.

> Exclude SCM patterns from ScenarioClassNameFinder
> -------------------------------------------------
>
>                 Key: JBEHAVE-207
>                 URL: https://jira.codehaus.org/browse/JBEHAVE-207
>             Project: JBehave
>          Issue Type: Improvement
>          Components: Core
>    Affects Versions: 2.3
>            Reporter: Mauro Talevi
>            Priority: Minor
(Continue reading)

Permalink | Reply | 0 comments |
headers
Mauro Talevi (JIRA | 3 Dec 2011 15:46

[jira] Commented: (JBEHAVE-207) Exclude SCM patterns from ScenarioClassNameFinder


    [
https://jira.codehaus.org/browse/JBEHAVE-207?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=284810#comment-284810
] 

Mauro Talevi commented on JBEHAVE-207:
--------------------------------------

Please open a new jira issue, and if possible add a mini project to reproduce problem.

> Exclude SCM patterns from ScenarioClassNameFinder
> -------------------------------------------------
>
>                 Key: JBEHAVE-207
>                 URL: https://jira.codehaus.org/browse/JBEHAVE-207
>             Project: JBehave
>          Issue Type: Improvement
>          Components: Core
>    Affects Versions: 2.3
>            Reporter: Mauro Talevi
>            Priority: Minor
>             Fix For: 2.5.6
>
>
> Automatically exclude .svn and other SCM directories from the directory scan.

--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
(Continue reading)

Permalink | Reply | 0 comments |
headers
Mauro Talevi (JIRA | 3 Dec 2011 15:48

[jira] Commented: (JBEHAVE-650) Ant copy-dependencies (binary distribution) doesn't find all required artifacts when the local maven cache is empty


    [
https://jira.codehaus.org/browse/JBEHAVE-650?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=284811#comment-284811
] 

Mauro Talevi commented on JBEHAVE-650:
--------------------------------------

Hi, can you try playing with the Maven anttasks to see if the problem is with the profiles? 

I suspect it may not be picking up the ones activated by default in settings.xml

> Ant copy-dependencies (binary distribution) doesn't find all required artifacts when the local maven
cache is empty
> -------------------------------------------------------------------------------------------------------------------
>
>                 Key: JBEHAVE-650
>                 URL: https://jira.codehaus.org/browse/JBEHAVE-650
>             Project: JBehave
>          Issue Type: Bug
>          Components: Build
>    Affects Versions: 3.5.4
>         Environment: ubuntu, ant 1.8.2
>            Reporter: Alexander Lehmann
>            Priority: Minor
>
> Starting with a local .m2 repository the doesn't have the files cached, ant copy-dependencies doesn't
find all necessary artifacts.
> (log shortened)
> BUILD FAILED
(Continue reading)

Permalink | Reply | 0 comments |
headers
Alexander Lehmann (JIRA | 3 Dec 2011 19:05

[jira] Commented: (JBEHAVE-650) Ant copy-dependencies (binary distribution) doesn't find all required artifacts when the local maven cache is empty


    [
https://jira.codehaus.org/browse/JBEHAVE-650?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=284819#comment-284819
] 

Alexander Lehmann commented on JBEHAVE-650:
-------------------------------------------

this is probably a bug in the maven-ant-tasks, there is at least one issue that describes a similar problem
(MANTTASKS-175), however the resolution works, if the settings are loaded by the pom task

> Ant copy-dependencies (binary distribution) doesn't find all required artifacts when the local maven
cache is empty
> -------------------------------------------------------------------------------------------------------------------
>
>                 Key: JBEHAVE-650
>                 URL: https://jira.codehaus.org/browse/JBEHAVE-650
>             Project: JBehave
>          Issue Type: Bug
>          Components: Build
>    Affects Versions: 3.5.4
>         Environment: ubuntu, ant 1.8.2
>            Reporter: Alexander Lehmann
>            Priority: Minor
>
> Starting with a local .m2 repository the doesn't have the files cached, ant copy-dependencies doesn't
find all necessary artifacts.
> (log shortened)
> BUILD FAILED
> /home/lehmann/jbehave/jbehave-3.5.4/lib/build.xml:7: Unable to resolve artifact: Missing:
(Continue reading)

Permalink | Reply | 0 comments |
headers
Alexander Lehmann (JIRA | 3 Dec 2011 19:19

[jira] Updated: (JBEHAVE-650) Ant copy-dependencies (binary distribution) doesn't find all required artifacts when the local maven cache is empty


     [
https://jira.codehaus.org/browse/JBEHAVE-650?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Alexander Lehmann updated JBEHAVE-650:
--------------------------------------

    Attachment: jbehave.diff

diff for lib/build.xml
(made with WinMerge, I hope that works)

> Ant copy-dependencies (binary distribution) doesn't find all required artifacts when the local maven
cache is empty
> -------------------------------------------------------------------------------------------------------------------
>
>                 Key: JBEHAVE-650
>                 URL: https://jira.codehaus.org/browse/JBEHAVE-650
>             Project: JBehave
>          Issue Type: Bug
>          Components: Build
>    Affects Versions: 3.5.4
>         Environment: ubuntu, ant 1.8.2
>            Reporter: Alexander Lehmann
>            Priority: Minor
>         Attachments: jbehave.diff
>
>
> Starting with a local .m2 repository the doesn't have the files cached, ant copy-dependencies doesn't
find all necessary artifacts.
(Continue reading)

Permalink | Reply | 0 comments |
headers
Mauro Talevi (JIRA | 3 Dec 2011 19:29

[jira] Resolved: (JBEHAVE-650) Ant copy-dependencies (binary distribution) doesn't find all required artifacts when the local maven cache is empty


     [
https://jira.codehaus.org/browse/JBEHAVE-650?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Mauro Talevi resolved JBEHAVE-650.
----------------------------------

       Resolution: Fixed
    Fix Version/s: 3.6

Applied patch with thanks.

> Ant copy-dependencies (binary distribution) doesn't find all required artifacts when the local maven
cache is empty
> -------------------------------------------------------------------------------------------------------------------
>
>                 Key: JBEHAVE-650
>                 URL: https://jira.codehaus.org/browse/JBEHAVE-650
>             Project: JBehave
>          Issue Type: Bug
>          Components: Build
>    Affects Versions: 3.5.4
>         Environment: ubuntu, ant 1.8.2
>            Reporter: Alexander Lehmann
>            Priority: Minor
>             Fix For: 3.6
>
>         Attachments: jbehave.diff
>
>
(Continue reading)

Permalink | Reply | 0 comments |
headers
Alexander Lehmann (JIRA | 3 Dec 2011 23:10

[jira] Commented: (JBEHAVE-430) build.xml may not work due to user rights and can change users {ant.home}/lib


    [
https://jira.codehaus.org/browse/JBEHAVE-430?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=284830#comment-284830
] 

Alexander Lehmann commented on JBEHAVE-430:
-------------------------------------------

this issue was resolved with JBEHAVE-634
(even though I noticed the problem in Windows, the cause of the issue is the same as this)

> build.xml may not work due to user rights and can change users {ant.home}/lib
> -----------------------------------------------------------------------------
>
>                 Key: JBEHAVE-430
>                 URL: https://jira.codehaus.org/browse/JBEHAVE-430
>             Project: JBehave
>          Issue Type: Bug
>          Components: Ant Tasks
>    Affects Versions: 3.1.2
>         Environment: linux ubuntu
>            Reporter: Zsolt Fabok
>            Priority: Minor
>
> Hi,
> The shipped build.xml of jbehave 3.1.2 has two targets: setup and copy-dependencies. The second one
depends on the first one, but under certain circumstances the setup task may fail, which will make the
copy-dependencies fail. For example if someone has a globally installed ant version (in case of ubuntu
apt-get install ant).
> ~/Desktop/jbehave-3.1.2/lib % ant
(Continue reading)

Permalink | Reply | 0 comments |
headers
Alexander Lehmann (JIRA | 3 Dec 2011 23:24

[jira] Created: (JBEHAVE-651) ant copy-depedencies improvments

ant copy-depedencies improvments
--------------------------------

                 Key: JBEHAVE-651
                 URL: https://jira.codehaus.org/browse/JBEHAVE-651
             Project: JBehave
          Issue Type: Improvement
          Components: Core
    Affects Versions: 3.5.4
         Environment: any
            Reporter: Alexander Lehmann
            Priority: Minor

I have 3 suggestions for improvements of the ant copy-dependencies process (or 2 suggestions and one question=

- update maven-ant-tasks to the current version (2.1.3)
- the maven-ant-tasks jar shouldn't be in lib (since it is not a dependency of jbehave) maybe if should be in a
subdir ant
- is it intentional that the binary distribution doesn't contain any binaries? It just downloads the
jbehave jars along with the dependencies.

--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira

---------------------------------------------------------------------
To unsubscribe from this list, please visit:

    http://xircles.codehaus.org/manage_email
(Continue reading)

Permalink | Reply | 4 comments |
headers
Mauro Talevi (JIRA | 4 Dec 2011 16:11

[jira] Updated: (JBEHAVE-651) ant copy-depedencies improvements


     [
https://jira.codehaus.org/browse/JBEHAVE-651?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Mauro Talevi updated JBEHAVE-651:
---------------------------------

    Fix Version/s: 3.6
          Summary: ant copy-depedencies improvements  (was: ant copy-depedencies improvments)

Please feel free to attach patch for first two points. 

Yes, it is intentional to avoid having big bloated distributions.  It's very easy to download and cache dependencies.

> ant copy-depedencies improvements
> ---------------------------------
>
>                 Key: JBEHAVE-651
>                 URL: https://jira.codehaus.org/browse/JBEHAVE-651
>             Project: JBehave
>          Issue Type: Improvement
>          Components: Core
>    Affects Versions: 3.5.4
>         Environment: any
>            Reporter: Alexander Lehmann
>            Priority: Minor
>             Fix For: 3.6
>
>
> I have 3 suggestions for improvements of the ant copy-dependencies process (or 2 suggestions and one question=
(Continue reading)

Permalink | Reply | 0 comments |
headers
Mauro Talevi (JIRA | 4 Dec 2011 16:21

[jira] Resolved: (JBEHAVE-430) build.xml may not work due to user rights and can change users {ant.home}/lib


     [
https://jira.codehaus.org/browse/JBEHAVE-430?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Mauro Talevi resolved JBEHAVE-430.
----------------------------------

       Resolution: Duplicate
    Fix Version/s: 3.6

Fixed by JBEHAVE-634.

> build.xml may not work due to user rights and can change users {ant.home}/lib
> -----------------------------------------------------------------------------
>
>                 Key: JBEHAVE-430
>                 URL: https://jira.codehaus.org/browse/JBEHAVE-430
>             Project: JBehave
>          Issue Type: Bug
>          Components: Ant Tasks
>    Affects Versions: 3.1.2
>         Environment: linux ubuntu
>            Reporter: Zsolt Fabok
>            Priority: Minor
>             Fix For: 3.6
>
>
> Hi,
> The shipped build.xml of jbehave 3.1.2 has two targets: setup and copy-dependencies. The second one
depends on the first one, but under certain circumstances the setup task may fail, which will make the
(Continue reading)

Permalink | Reply | 0 comments |

Gmane