[jira] Updated: (MNG-5136) Not all dependency are included in WAR
[ https://jira.codehaus.org/browse/MNG-5136?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] luca preziati updated MNG-5136: --- Attachment: tree.TXT mvn dependency:tree result > Not all dependency are included in WAR > -- > > Key: MNG-5136 > URL: https://jira.codehaus.org/browse/MNG-5136 > Project: Maven 2 & 3 > Issue Type: Bug > Components: General >Affects Versions: 3.0.3 > Environment: Windows Vista 32 Bit, apache maven 3.0.3, java version > "1.6.0_21" > Java(TM) SE Runtime Environment (build 1.6.0_21-b07) > Java HotSpot(TM) Client VM (build 17.0-b17, mixed mode, sharing) >Reporter: luca preziati >Priority: Blocker > Attachments: Lib dir.txt, list.txt, tree.TXT > > > When I launch mvn dependency:tree i found logback-core, when I build War the > lib isn't include. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Commented: (MNG-5136) Not all dependency are included in WAR
[ https://jira.codehaus.org/browse/MNG-5136?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=274331#comment-274331 ] luca preziati commented on MNG-5136: Logback-core is dependency of logback-classic. And logback-classic is dependency of parent project. Logback-classic have this pom: ... ch.qos.logback logback-core compile I dependency:tree is what I need in my project. The dependency:list is whitout logback-core and javassist > Not all dependency are included in WAR > -- > > Key: MNG-5136 > URL: https://jira.codehaus.org/browse/MNG-5136 > Project: Maven 2 & 3 > Issue Type: Bug > Components: General >Affects Versions: 3.0.3 > Environment: Windows Vista 32 Bit, apache maven 3.0.3, java version > "1.6.0_21" > Java(TM) SE Runtime Environment (build 1.6.0_21-b07) > Java HotSpot(TM) Client VM (build 17.0-b17, mixed mode, sharing) >Reporter: luca preziati >Priority: Blocker > Attachments: Lib dir.txt, list.txt, tree.TXT > > > When I launch mvn dependency:tree i found logback-core, when I build War the > lib isn't include. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Updated: (MNG-5136) Not all dependency are included in WAR
[ https://jira.codehaus.org/browse/MNG-5136?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] luca preziati updated MNG-5136: --- Attachment: list.txt mvn dependency:list result > Not all dependency are included in WAR > -- > > Key: MNG-5136 > URL: https://jira.codehaus.org/browse/MNG-5136 > Project: Maven 2 & 3 > Issue Type: Bug > Components: General >Affects Versions: 3.0.3 > Environment: Windows Vista 32 Bit, apache maven 3.0.3, java version > "1.6.0_21" > Java(TM) SE Runtime Environment (build 1.6.0_21-b07) > Java HotSpot(TM) Client VM (build 17.0-b17, mixed mode, sharing) >Reporter: luca preziati >Priority: Blocker > Attachments: Lib dir.txt, list.txt, tree.TXT > > > When I launch mvn dependency:tree i found logback-core, when I build War the > lib isn't include. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Commented: (MNG-5136) Not all dependency are included in WAR
[ https://jira.codehaus.org/browse/MNG-5136?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=274334#comment-274334 ] luca preziati commented on MNG-5136: How can I export a log debug? Thanks in advance. I don't know if I can give you a copy of the project. Of the pom surely. > Not all dependency are included in WAR > -- > > Key: MNG-5136 > URL: https://jira.codehaus.org/browse/MNG-5136 > Project: Maven 2 & 3 > Issue Type: Bug > Components: General >Affects Versions: 3.0.3 > Environment: Windows Vista 32 Bit, apache maven 3.0.3, java version > "1.6.0_21" > Java(TM) SE Runtime Environment (build 1.6.0_21-b07) > Java HotSpot(TM) Client VM (build 17.0-b17, mixed mode, sharing) >Reporter: luca preziati >Priority: Blocker > Attachments: Lib dir.txt, list.txt, tree.TXT > > > When I launch mvn dependency:tree i found logback-core, when I build War the > lib isn't include. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Commented: (MNG-5064) mvn -nsu (--no-snapshot-updates) should not download snapshots (and break local builds)
[
https://jira.codehaus.org/browse/MNG-5064?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=274335#comment-274335
]
Geoffrey De Smet commented on MNG-5064:
---
Yet I have replicated it a couple of days on the command line. Strange.
Maybe, there's a difference between the command line and the test environment?
I am using maven 3.0.3.
Here's a replication of what I did (although there's might be a shorter
reproduce recipe):
{code}
// Use maven 3.0.3 on linux
$ git clone g...@github.com:droolsjbpm/droolsjbpm-build-bootstrap.git
// clones droolsjbpm-knowledge, then drools, then drools-planner, ...
$ droolsjbpm-build-bootstrap/script/git-clone-others.sh
// builds droolsjbpm-knowledge, then drools, then drools-planner, ...
$ droolsjbpm-build-bootstrap/script/mvn-all.sh clean install -DskipTests
// Note: drools-planner depends on a SNAPSHOT of drools
// Wait one day
$ cd drools-planner
$ mvn clean install -nsu -DskipTests
// It downloads drools-20110727-... pom and jar
{code}
> mvn -nsu (--no-snapshot-updates) should not download snapshots (and break
> local builds)
> ---
>
> Key: MNG-5064
> URL: https://jira.codehaus.org/browse/MNG-5064
> Project: Maven 2 & 3
> Issue Type: Bug
> Components: Command Line
>Affects Versions: 3.0.3
>Reporter: Geoffrey De Smet
>Assignee: Benson Margulies
>Priority: Critical
>
> Here's the command I ran (on a fresh morning, because our update policy is
> daily and our SNAPSHOTs are deployed by Hudson at night, with maven 3.0.3):
> {code}
> $ mvn -nsu clean install -DskipTests
> [INFO] Scanning for projects...
> Downloading:
> http://repository.jboss.org/nexus/content/groups/public/org/drools/droolsjbpm-parent/5.2.0-SNAPSHOT/maven-metadata.xml
> ...
> [INFO]
>
> [INFO] Building Drools Planner core 5.2.0-SNAPSHOT
> [INFO]
>
> Downloading:
> http://repository.jboss.org/nexus/content/groups/public/org/drools/knowledge-api/5.2.0-SNAPSHOT/maven-metadata.xml
> Downloaded:
> http://repository.jboss.org/nexus/content/groups/public/org/drools/knowledge-api/5.2.0-SNAPSHOT/maven-metadata.xml
> (2 KB at 1.8 KB/sec)
> Downloading:
> http://repository.jboss.org/nexus/content/groups/public/org/drools/knowledge-api/5.2.0-SNAPSHOT/knowledge-api-5.2.0-20110413.010206-9.pom
> Downloaded:
> http://repository.jboss.org/nexus/content/groups/public/org/drools/knowledge-api/5.2.0-SNAPSHOT/knowledge-api-5.2.0-20110413.010206-9.pom
> (6 KB at 6.0 KB/sec)
> ...
> Downloading:
> http://repository.jboss.org/nexus/content/groups/public/org/drools/knowledge-api/5.2.0-SNAPSHOT/knowledge-api-5.2.0-20110413.010206-9.jar
> ...
> {code}
> Despite that I added "-nsu" (also known as "--no-snapshot-updates"), it
> downloaded snapshots.
> This is a pretty bad thing, because if I hadn't pulled in days (and just
> wanted to test my local changes before merging in remote changes),
> this would have broke my build, for example:
> - because the parent pom in downloaded SNAPSHOT had a dependency removed
> which my local pom was still using (because I hadn't pulled the changes yet)
> - because the downloaded knowledge-api changed a non-released method
> signature (and I hadn't pulled the changes to deal with that yet).
> - ...
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Commented: (MNG-5064) mvn -nsu (--no-snapshot-updates) should not download snapshots (and break local builds)
[
https://jira.codehaus.org/browse/MNG-5064?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=274336#comment-274336
]
Geoffrey De Smet commented on MNG-5064:
---
Note, we do have this is in our parent pom:
{code}
jboss-public-repository-group
...
true
daily
{code}
But the -nsu should take precedence over that updatePolicy=daily
> mvn -nsu (--no-snapshot-updates) should not download snapshots (and break
> local builds)
> ---
>
> Key: MNG-5064
> URL: https://jira.codehaus.org/browse/MNG-5064
> Project: Maven 2 & 3
> Issue Type: Bug
> Components: Command Line
>Affects Versions: 3.0.3
>Reporter: Geoffrey De Smet
>Assignee: Benson Margulies
>Priority: Critical
>
> Here's the command I ran (on a fresh morning, because our update policy is
> daily and our SNAPSHOTs are deployed by Hudson at night, with maven 3.0.3):
> {code}
> $ mvn -nsu clean install -DskipTests
> [INFO] Scanning for projects...
> Downloading:
> http://repository.jboss.org/nexus/content/groups/public/org/drools/droolsjbpm-parent/5.2.0-SNAPSHOT/maven-metadata.xml
> ...
> [INFO]
>
> [INFO] Building Drools Planner core 5.2.0-SNAPSHOT
> [INFO]
>
> Downloading:
> http://repository.jboss.org/nexus/content/groups/public/org/drools/knowledge-api/5.2.0-SNAPSHOT/maven-metadata.xml
> Downloaded:
> http://repository.jboss.org/nexus/content/groups/public/org/drools/knowledge-api/5.2.0-SNAPSHOT/maven-metadata.xml
> (2 KB at 1.8 KB/sec)
> Downloading:
> http://repository.jboss.org/nexus/content/groups/public/org/drools/knowledge-api/5.2.0-SNAPSHOT/knowledge-api-5.2.0-20110413.010206-9.pom
> Downloaded:
> http://repository.jboss.org/nexus/content/groups/public/org/drools/knowledge-api/5.2.0-SNAPSHOT/knowledge-api-5.2.0-20110413.010206-9.pom
> (6 KB at 6.0 KB/sec)
> ...
> Downloading:
> http://repository.jboss.org/nexus/content/groups/public/org/drools/knowledge-api/5.2.0-SNAPSHOT/knowledge-api-5.2.0-20110413.010206-9.jar
> ...
> {code}
> Despite that I added "-nsu" (also known as "--no-snapshot-updates"), it
> downloaded snapshots.
> This is a pretty bad thing, because if I hadn't pulled in days (and just
> wanted to test my local changes before merging in remote changes),
> this would have broke my build, for example:
> - because the parent pom in downloaded SNAPSHOT had a dependency removed
> which my local pom was still using (because I hadn't pulled the changes yet)
> - because the downloaded knowledge-api changed a non-released method
> signature (and I hadn't pulled the changes to deal with that yet).
> - ...
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Issue Comment Edited: (MNG-5064) mvn -nsu (--no-snapshot-updates) should not download snapshots (and break local builds)
[
https://jira.codehaus.org/browse/MNG-5064?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=274336#comment-274336
]
Geoffrey De Smet edited comment on MNG-5064 at 7/27/11 3:13 AM:
Note, we do have this is in our parent pom:
{code}
jboss-public-repository-group
...
true
daily
{code}
But the -nsu should take precedence over that updatePolicy=daily, because
command line always overwrites configuration.
The workflow is:
- Either you've just git pulled, so you mvn build to fetch the latest snapshot
(as previous snapshots might be binary incompatible)
- Or, you've haven't git pulled in a while, so you mvn -nsu build to verify
your local changes and you don't want the latest snapshot (which might be
binary incompatible)
was (Author: ge0ffrey):
Note, we do have this is in our parent pom:
{code}
jboss-public-repository-group
...
true
daily
{code}
But the -nsu should take precedence over that updatePolicy=daily
> mvn -nsu (--no-snapshot-updates) should not download snapshots (and break
> local builds)
> ---
>
> Key: MNG-5064
> URL: https://jira.codehaus.org/browse/MNG-5064
> Project: Maven 2 & 3
> Issue Type: Bug
> Components: Command Line
>Affects Versions: 3.0.3
>Reporter: Geoffrey De Smet
>Assignee: Benson Margulies
>Priority: Critical
>
> Here's the command I ran (on a fresh morning, because our update policy is
> daily and our SNAPSHOTs are deployed by Hudson at night, with maven 3.0.3):
> {code}
> $ mvn -nsu clean install -DskipTests
> [INFO] Scanning for projects...
> Downloading:
> http://repository.jboss.org/nexus/content/groups/public/org/drools/droolsjbpm-parent/5.2.0-SNAPSHOT/maven-metadata.xml
> ...
> [INFO]
>
> [INFO] Building Drools Planner core 5.2.0-SNAPSHOT
> [INFO]
>
> Downloading:
> http://repository.jboss.org/nexus/content/groups/public/org/drools/knowledge-api/5.2.0-SNAPSHOT/maven-metadata.xml
> Downloaded:
> http://repository.jboss.org/nexus/content/groups/public/org/drools/knowledge-api/5.2.0-SNAPSHOT/maven-metadata.xml
> (2 KB at 1.8 KB/sec)
> Downloading:
> http://repository.jboss.org/nexus/content/groups/public/org/drools/knowledge-api/5.2.0-SNAPSHOT/knowledge-api-5.2.0-20110413.010206-9.pom
> Downloaded:
> http://repository.jboss.org/nexus/content/groups/public/org/drools/knowledge-api/5.2.0-SNAPSHOT/knowledge-api-5.2.0-20110413.010206-9.pom
> (6 KB at 6.0 KB/sec)
> ...
> Downloading:
> http://repository.jboss.org/nexus/content/groups/public/org/drools/knowledge-api/5.2.0-SNAPSHOT/knowledge-api-5.2.0-20110413.010206-9.jar
> ...
> {code}
> Despite that I added "-nsu" (also known as "--no-snapshot-updates"), it
> downloaded snapshots.
> This is a pretty bad thing, because if I hadn't pulled in days (and just
> wanted to test my local changes before merging in remote changes),
> this would have broke my build, for example:
> - because the parent pom in downloaded SNAPSHOT had a dependency removed
> which my local pom was still using (because I hadn't pulled the changes yet)
> - because the downloaded knowledge-api changed a non-released method
> signature (and I hadn't pulled the changes to deal with that yet).
> - ...
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Issue Comment Edited: (MNG-5064) mvn -nsu (--no-snapshot-updates) should not download snapshots (and break local builds)
[
https://jira.codehaus.org/browse/MNG-5064?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=274336#comment-274336
]
Geoffrey De Smet edited comment on MNG-5064 at 7/27/11 3:13 AM:
Note, we do have this is in our parent pom:
{code}
jboss-public-repository-group
...
true
daily
{code}
But the -nsu should take precedence over that updatePolicy=daily, because
command line always overwrites configuration.
The workflow is:
- Either you've just git pulled, so you mvn build to fetch the latest snapshot
(as previous snapshots might be binary incompatible with the latest code)
- Or, you've haven't git pulled in a while, so you mvn -nsu build to verify
your local changes and you don't want the latest snapshot (which might be
binary incompatible because you don't have the latest code)
was (Author: ge0ffrey):
Note, we do have this is in our parent pom:
{code}
jboss-public-repository-group
...
true
daily
{code}
But the -nsu should take precedence over that updatePolicy=daily, because
command line always overwrites configuration.
The workflow is:
- Either you've just git pulled, so you mvn build to fetch the latest snapshot
(as previous snapshots might be binary incompatible)
- Or, you've haven't git pulled in a while, so you mvn -nsu build to verify
your local changes and you don't want the latest snapshot (which might be
binary incompatible)
> mvn -nsu (--no-snapshot-updates) should not download snapshots (and break
> local builds)
> ---
>
> Key: MNG-5064
> URL: https://jira.codehaus.org/browse/MNG-5064
> Project: Maven 2 & 3
> Issue Type: Bug
> Components: Command Line
>Affects Versions: 3.0.3
>Reporter: Geoffrey De Smet
>Assignee: Benson Margulies
>Priority: Critical
>
> Here's the command I ran (on a fresh morning, because our update policy is
> daily and our SNAPSHOTs are deployed by Hudson at night, with maven 3.0.3):
> {code}
> $ mvn -nsu clean install -DskipTests
> [INFO] Scanning for projects...
> Downloading:
> http://repository.jboss.org/nexus/content/groups/public/org/drools/droolsjbpm-parent/5.2.0-SNAPSHOT/maven-metadata.xml
> ...
> [INFO]
>
> [INFO] Building Drools Planner core 5.2.0-SNAPSHOT
> [INFO]
>
> Downloading:
> http://repository.jboss.org/nexus/content/groups/public/org/drools/knowledge-api/5.2.0-SNAPSHOT/maven-metadata.xml
> Downloaded:
> http://repository.jboss.org/nexus/content/groups/public/org/drools/knowledge-api/5.2.0-SNAPSHOT/maven-metadata.xml
> (2 KB at 1.8 KB/sec)
> Downloading:
> http://repository.jboss.org/nexus/content/groups/public/org/drools/knowledge-api/5.2.0-SNAPSHOT/knowledge-api-5.2.0-20110413.010206-9.pom
> Downloaded:
> http://repository.jboss.org/nexus/content/groups/public/org/drools/knowledge-api/5.2.0-SNAPSHOT/knowledge-api-5.2.0-20110413.010206-9.pom
> (6 KB at 6.0 KB/sec)
> ...
> Downloading:
> http://repository.jboss.org/nexus/content/groups/public/org/drools/knowledge-api/5.2.0-SNAPSHOT/knowledge-api-5.2.0-20110413.010206-9.jar
> ...
> {code}
> Despite that I added "-nsu" (also known as "--no-snapshot-updates"), it
> downloaded snapshots.
> This is a pretty bad thing, because if I hadn't pulled in days (and just
> wanted to test my local changes before merging in remote changes),
> this would have broke my build, for example:
> - because the parent pom in downloaded SNAPSHOT had a dependency removed
> which my local pom was still using (because I hadn't pulled the changes yet)
> - because the downloaded knowledge-api changed a non-released method
> signature (and I hadn't pulled the changes to deal with that yet).
> - ...
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Commented: (MRELEASE-605) when not pushing changes to remote git repo in 2.1, the release plugin fails on release:perform
[
https://jira.codehaus.org/browse/MRELEASE-605?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=274346#comment-274346
]
james strachan commented on MRELEASE-605:
-
Just wanted to say a big thank you! Works like a charm. Its made one geek very
happy :). Just did a release without having to muck about with connectionUrl -
yay!
> when not pushing changes to remote git repo in 2.1, the release plugin fails
> on release:perform
> ---
>
> Key: MRELEASE-605
> URL: https://jira.codehaus.org/browse/MRELEASE-605
> Project: Maven 2.x Release Plugin
> Issue Type: Improvement
>Affects Versions: 2.1
>Reporter: james strachan
>Assignee: Mark Struberg
> Fix For: 2.2
>
>
> as it tries to clone the remote repo, which has not yet been pushed - so
> there's no tag in the remote repo yet.
> Ideally if pushChanges is false, it should use a value of
> {code}
>
> scm:git:file://${baseDir}
> ...
>
> {code}
> so that it clones from the current local git repo (which has everything
> inside it) rather than the remote repo which has yet to be pushed.
> BTW a great use case for not pushing is using a staging maven repo like
> Nexus; which may reject an attempt to promote a staged build, so you only
> want to push after a downstream stage works.
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Commented: (MNG-5136) Not all dependency are included in WAR
[
https://jira.codehaus.org/browse/MNG-5136?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=274349#comment-274349
]
Benjamin Bentmann commented on MNG-5136:
{{mvn goal -X > debug.log}}, I would also like to point out the [introduction
page|http://jira.codehaus.org/browse/MNG] to this issue tracking project which
provides this information.
> Not all dependency are included in WAR
> --
>
> Key: MNG-5136
> URL: https://jira.codehaus.org/browse/MNG-5136
> Project: Maven 2 & 3
> Issue Type: Bug
> Components: General
>Affects Versions: 3.0.3
> Environment: Windows Vista 32 Bit, apache maven 3.0.3, java version
> "1.6.0_21"
> Java(TM) SE Runtime Environment (build 1.6.0_21-b07)
> Java HotSpot(TM) Client VM (build 17.0-b17, mixed mode, sharing)
>Reporter: luca preziati
>Priority: Blocker
> Attachments: Lib dir.txt, list.txt, tree.TXT
>
>
> When I launch mvn dependency:tree i found logback-core, when I build War the
> lib isn't include.
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Updated: (MNG-5136) Not all dependency are included in WAR
[ https://jira.codehaus.org/browse/MNG-5136?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] luca preziati updated MNG-5136: --- Attachment: build-MAVEN-3.0.3.log This is the log file of the build outside eclipse, from Shell with maven 3.0.3. I have some collegues with Mac Os and same version of maven and they don't have this problem. Anotehr one with Windows Seven 64 bit have same problem. > Not all dependency are included in WAR > -- > > Key: MNG-5136 > URL: https://jira.codehaus.org/browse/MNG-5136 > Project: Maven 2 & 3 > Issue Type: Bug > Components: General >Affects Versions: 3.0.3 > Environment: Windows Vista 32 Bit, apache maven 3.0.3, java version > "1.6.0_21" > Java(TM) SE Runtime Environment (build 1.6.0_21-b07) > Java HotSpot(TM) Client VM (build 17.0-b17, mixed mode, sharing) >Reporter: luca preziati >Priority: Blocker > Attachments: build-MAVEN-3.0.3.log, Lib dir.txt, list.txt, tree.TXT > > > When I launch mvn dependency:tree i found logback-core, when I build War the > lib isn't include. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Updated: (MNG-5136) Not all dependency are included in WAR
[ https://jira.codehaus.org/browse/MNG-5136?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] luca preziati updated MNG-5136: --- Attachment: build-MAVEN-3.0-SNAPSHOT build made from eclipse, Helios SR2, plugin maven 0.10.0.20100209-0800. > Not all dependency are included in WAR > -- > > Key: MNG-5136 > URL: https://jira.codehaus.org/browse/MNG-5136 > Project: Maven 2 & 3 > Issue Type: Bug > Components: General >Affects Versions: 3.0.3 > Environment: Windows Vista 32 Bit, apache maven 3.0.3, java version > "1.6.0_21" > Java(TM) SE Runtime Environment (build 1.6.0_21-b07) > Java HotSpot(TM) Client VM (build 17.0-b17, mixed mode, sharing) >Reporter: luca preziati >Priority: Blocker > Attachments: build-MAVEN-3.0.3.log, build-MAVEN-3.0-SNAPSHOT, Lib > dir.txt, list.txt, tree.TXT > > > When I launch mvn dependency:tree i found logback-core, when I build War the > lib isn't include. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Closed: (MNG-5064) mvn -nsu (--no-snapshot-updates) should not download snapshots (and break local builds)
[
https://jira.codehaus.org/browse/MNG-5064?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Benjamin Bentmann closed MNG-5064.
--
Resolution: Fixed
Fix Version/s: 3.0.4
Assignee: Benjamin Bentmann (was: Benson Margulies)
Fixed in [r1151418|http://svn.apache.org/viewvc?view=revision&revision=1151418].
> mvn -nsu (--no-snapshot-updates) should not download snapshots (and break
> local builds)
> ---
>
> Key: MNG-5064
> URL: https://jira.codehaus.org/browse/MNG-5064
> Project: Maven 2 & 3
> Issue Type: Bug
> Components: Command Line
>Affects Versions: 3.0.3
>Reporter: Geoffrey De Smet
>Assignee: Benjamin Bentmann
>Priority: Critical
> Fix For: 3.0.4
>
>
> Here's the command I ran (on a fresh morning, because our update policy is
> daily and our SNAPSHOTs are deployed by Hudson at night, with maven 3.0.3):
> {code}
> $ mvn -nsu clean install -DskipTests
> [INFO] Scanning for projects...
> Downloading:
> http://repository.jboss.org/nexus/content/groups/public/org/drools/droolsjbpm-parent/5.2.0-SNAPSHOT/maven-metadata.xml
> ...
> [INFO]
>
> [INFO] Building Drools Planner core 5.2.0-SNAPSHOT
> [INFO]
>
> Downloading:
> http://repository.jboss.org/nexus/content/groups/public/org/drools/knowledge-api/5.2.0-SNAPSHOT/maven-metadata.xml
> Downloaded:
> http://repository.jboss.org/nexus/content/groups/public/org/drools/knowledge-api/5.2.0-SNAPSHOT/maven-metadata.xml
> (2 KB at 1.8 KB/sec)
> Downloading:
> http://repository.jboss.org/nexus/content/groups/public/org/drools/knowledge-api/5.2.0-SNAPSHOT/knowledge-api-5.2.0-20110413.010206-9.pom
> Downloaded:
> http://repository.jboss.org/nexus/content/groups/public/org/drools/knowledge-api/5.2.0-SNAPSHOT/knowledge-api-5.2.0-20110413.010206-9.pom
> (6 KB at 6.0 KB/sec)
> ...
> Downloading:
> http://repository.jboss.org/nexus/content/groups/public/org/drools/knowledge-api/5.2.0-SNAPSHOT/knowledge-api-5.2.0-20110413.010206-9.jar
> ...
> {code}
> Despite that I added "-nsu" (also known as "--no-snapshot-updates"), it
> downloaded snapshots.
> This is a pretty bad thing, because if I hadn't pulled in days (and just
> wanted to test my local changes before merging in remote changes),
> this would have broke my build, for example:
> - because the parent pom in downloaded SNAPSHOT had a dependency removed
> which my local pom was still using (because I hadn't pulled the changes yet)
> - because the downloaded knowledge-api changed a non-released method
> signature (and I hadn't pulled the changes to deal with that yet).
> - ...
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Closed: (MNG-5131) Wrong encoding for encrypted passwords
[ https://jira.codehaus.org/browse/MNG-5131?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Benjamin Bentmann closed MNG-5131. -- Resolution: Fixed Fix Version/s: 3.0.4 Assignee: Benjamin Bentmann Updated to plexus-cipher:1.7 in [r1151419|http://svn.apache.org/viewvc?view=revision&revision=1151419] which contains your fix, thanks. > Wrong encoding for encrypted passwords > -- > > Key: MNG-5131 > URL: https://jira.codehaus.org/browse/MNG-5131 > Project: Maven 2 & 3 > Issue Type: Bug > Components: Command Line, Settings >Affects Versions: 3.0.3 > Environment: all >Reporter: Conny Kreyssel >Assignee: Benjamin Bentmann > Fix For: 3.0.4 > > > The plexus-cipher-component has a bug that encodes the crypted passwords > wrong. > I has submited a patch for that component on github. > https://github.com/sonatype/plexus-cipher/pull/1 > Please include this fix if the new plexus-cipher is released. > Thanks. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Updated: (MNG-5131) Wrong encoding for encrypted passwords
[ https://jira.codehaus.org/browse/MNG-5131?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Benjamin Bentmann updated MNG-5131: --- Component/s: (was: Reactor and workspace) Settings Command Line > Wrong encoding for encrypted passwords > -- > > Key: MNG-5131 > URL: https://jira.codehaus.org/browse/MNG-5131 > Project: Maven 2 & 3 > Issue Type: Bug > Components: Command Line, Settings >Affects Versions: 3.0.3 > Environment: all >Reporter: Conny Kreyssel > Fix For: 3.0.4 > > > The plexus-cipher-component has a bug that encodes the crypted passwords > wrong. > I has submited a patch for that component on github. > https://github.com/sonatype/plexus-cipher/pull/1 > Please include this fix if the new plexus-cipher is released. > Thanks. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Closed: (MNG-5113) NullPointerException on javadoc site generation
[
https://jira.codehaus.org/browse/MNG-5113?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Benjamin Bentmann closed MNG-5113.
--
Resolution: Fixed
Fix Version/s: 3.0.4
Assignee: Benjamin Bentmann
Fixed in [r1151420|http://svn.apache.org/viewvc?view=revision&revision=1151420].
> NullPointerException on javadoc site generation
> ---
>
> Key: MNG-5113
> URL: https://jira.codehaus.org/browse/MNG-5113
> Project: Maven 2 & 3
> Issue Type: Bug
> Components: Sites & Reporting
>Affects Versions: 3.0.3
> Environment: Archlinux 2.6.36 (x86)
>Reporter: Christian
>Assignee: Benjamin Bentmann
> Fix For: 3.0.4
>
> Attachments: debug.log, pom.xml
>
>
> Dear codehaus developers,
> Today I encountered a pretty serious error, while trying to generate javadocs
> for my code. This was the first time I added the reporting part to my pom.
> Site generation worked fine without this part. After I added this part, maven
> gave me a NullPointerException.
> It was very easy for me to reproduce the bug. I created an empty directory
> and put the following pom there:
> {code:xml|title=pom.xml}
>
> http://maven.apache.org/POM/4.0.0
> http://maven.apache.org/xsd/maven-4.0.0.xsd";
> xmlns="http://maven.apache.org/POM/4.0.0";
> xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance";>
> 4.0.0
> Test
> test
> 1.0-SNAPSHOT
>
>
>
> org.apache.maven.plugins
> maven-javadoc-plugin
> 2.8
>
>
>
>
> {code}
> Then I ran:
> {code}mvn site{code}
> I've attached the debugging output and this example pom to this report.
> Best regards,
> Chris
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Updated: (MNG-5137) Reactor resolution does not work for forked multi module builds
[
https://jira.codehaus.org/browse/MNG-5137?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Benjamin Bentmann updated MNG-5137:
---
Component/s: Reactor and workspace
> Reactor resolution does not work for forked multi module builds
> ---
>
> Key: MNG-5137
> URL: https://jira.codehaus.org/browse/MNG-5137
> Project: Maven 2 & 3
> Issue Type: Bug
> Components: Reactor and workspace
>Affects Versions: 2.2.1, 3.0.3
>Reporter: Benjamin Bentmann
>Assignee: Benjamin Bentmann
> Fix For: 3.0.4
>
> Attachments: test.zip
>
>
> Running {{mvn clean package site}} on the attached multi-module test project
> fails with a dependency resolution issue. While the main build still builds
> the aggregator module, an aggregator (report) mojo forks the lifecycle and
> despite this forked lifecycle executing up to "package" phase, reactor
> resolution inside this forked lifecycle fails since the wrong project
> instances (those from the main build instead of the forked build) are
> searched for build output.
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Closed: (MNG-5137) Reactor resolution does not work for forked multi module builds
[
https://jira.codehaus.org/browse/MNG-5137?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Benjamin Bentmann closed MNG-5137.
--
Resolution: Fixed
Fix Version/s: 3.0.4
Assignee: Benjamin Bentmann
Fixed in [r1151421|http://svn.apache.org/viewvc?view=revision&revision=1151421].
> Reactor resolution does not work for forked multi module builds
> ---
>
> Key: MNG-5137
> URL: https://jira.codehaus.org/browse/MNG-5137
> Project: Maven 2 & 3
> Issue Type: Bug
> Components: Reactor and workspace
>Affects Versions: 2.2.1, 3.0.3
>Reporter: Benjamin Bentmann
>Assignee: Benjamin Bentmann
> Fix For: 3.0.4
>
> Attachments: test.zip
>
>
> Running {{mvn clean package site}} on the attached multi-module test project
> fails with a dependency resolution issue. While the main build still builds
> the aggregator module, an aggregator (report) mojo forks the lifecycle and
> despite this forked lifecycle executing up to "package" phase, reactor
> resolution inside this forked lifecycle fails since the wrong project
> instances (those from the main build instead of the forked build) are
> searched for build output.
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Closed: (MNG-5096) on with test-jar doesn't work in maven 3
[
https://jira.codehaus.org/browse/MNG-5096?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Benjamin Bentmann closed MNG-5096.
--
Resolution: Fixed
Fix Version/s: 3.0.4
Assignee: Benjamin Bentmann
Fixed in [r1151423|http://svn.apache.org/viewvc?view=revision&revision=1151423].
> on with test-jar doesn't work in maven 3
> --
>
> Key: MNG-5096
> URL: https://jira.codehaus.org/browse/MNG-5096
> Project: Maven 2 & 3
> Issue Type: Bug
>Affects Versions: 3.0.3
> Environment: Ubuntu 10.04
>Reporter: Garrett Wu
>Assignee: Benjamin Bentmann
> Fix For: 3.0.4
>
> Attachments: maven-testcase.tar.gz
>
>
> There appears to be a regression in maven 3 that breaks test-jar dependency
> exclusions. I've attached a simple example to reproduce this. There are two
> projects: foo and bar. Project foo produces a test-jar artifact. Project
> bar depends on foo's test-jar but excludes a dependency on junit. In maven
> 2, a dependency:list shows that junit has successfully been excluded. In
> maven 3, a dependency:list shows that junit was not successfully excluded.
> To reproduce, download the {{maven-testcase.tar.gz}} attachment and run:
> {code:none}
> $ tar xzvf maven-testcase.tar.gz
> $ cd maven-testcase/foo
> $ mvn2 install
> $ cd ../bar
> $ mvn2 dependency:list
> ...
> [INFO] The following files have been resolved:
> [INFO]org.apache.maven:foo:test-jar:tests:1.0:test
> ...
> $ mvn3 dependency:list
> ...
> [INFO] The following files have been resolved:
> [INFO]junit:junit:jar:4.8.1:test
> [INFO]org.apache.maven:foo:test-jar:tests:1.0:test
> ...
> {code}
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Closed: (MNG-5135) Regression: in some cases aggregator mojo is unable to resolve dependencies with custom packaging
[ https://jira.codehaus.org/browse/MNG-5135?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Benjamin Bentmann closed MNG-5135. -- Resolution: Fixed Fix Version/s: 3.0.4 Assignee: Benjamin Bentmann Fixed in [r1151424|http://svn.apache.org/viewvc?view=revision&revision=1151424]. > Regression: in some cases aggregator mojo is unable to resolve dependencies > with custom packaging > - > > Key: MNG-5135 > URL: https://jira.codehaus.org/browse/MNG-5135 > Project: Maven 2 & 3 > Issue Type: Bug >Affects Versions: 3.0.3 > Environment: Maven 3.0.3 >Reporter: Evgeny Mandrikov >Assignee: Benjamin Bentmann > Fix For: 3.0.4 > > > As described in SONAR-2626 : aggregator mojo, which requires dependency > resolution (like "sonar:sonar" or "javadoc:aggregate-jar") is unable to > resolve dependencies, when executed from command-line and build extension > with custom packaging declared in sub-module, but not in parent. Declaration > of extension in parent allows to workaround problem as well as downgrade to > Maven 2.2.1 and execution of "mvn validate sonar:sonar". -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Commented: (MNG-5135) Regression: in some cases aggregator mojo is unable to resolve dependencies with custom packaging
[ https://jira.codehaus.org/browse/MNG-5135?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=274373#comment-274373 ] Evgeny Mandrikov commented on MNG-5135: --- Benjamin, thank you! BTW, is there any plans for release of 3.0.4? > Regression: in some cases aggregator mojo is unable to resolve dependencies > with custom packaging > - > > Key: MNG-5135 > URL: https://jira.codehaus.org/browse/MNG-5135 > Project: Maven 2 & 3 > Issue Type: Bug >Affects Versions: 3.0.3 > Environment: Maven 3.0.3 >Reporter: Evgeny Mandrikov >Assignee: Benjamin Bentmann > Fix For: 3.0.4 > > > As described in SONAR-2626 : aggregator mojo, which requires dependency > resolution (like "sonar:sonar" or "javadoc:aggregate-jar") is unable to > resolve dependencies, when executed from command-line and build extension > with custom packaging declared in sub-module, but not in parent. Declaration > of extension in parent allows to workaround problem as well as downgrade to > Maven 2.2.1 and execution of "mvn validate sonar:sonar". -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Commented: (MNG-5136) Not all dependency are included in WAR
[
https://jira.codehaus.org/browse/MNG-5136?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=274387#comment-274387
]
Benjamin Bentmann commented on MNG-5136:
Even with the debug log from Maven 3.0.3 I don't see any obvious hint to start
troubleshooting. You can try replacing all {{aether-\*-1.11.jar}} in your
{{/lib}} directory with their version 1.12 counterparts (as found
in [central|http://repo1.maven.org/maven2/org/sonatype/aether/]) and see
whether this solves the issue. That still failing, we would either need a
standalone POM to reproduce the issue or find ways to improve the debug logging
for the resolution process.
> Not all dependency are included in WAR
> --
>
> Key: MNG-5136
> URL: https://jira.codehaus.org/browse/MNG-5136
> Project: Maven 2 & 3
> Issue Type: Bug
> Components: General
>Affects Versions: 3.0.3
> Environment: Windows Vista 32 Bit, apache maven 3.0.3, java version
> "1.6.0_21"
> Java(TM) SE Runtime Environment (build 1.6.0_21-b07)
> Java HotSpot(TM) Client VM (build 17.0-b17, mixed mode, sharing)
>Reporter: luca preziati
>Priority: Blocker
> Attachments: build-MAVEN-3.0.3.log, build-MAVEN-3.0-SNAPSHOT, Lib
> dir.txt, list.txt, tree.TXT
>
>
> When I launch mvn dependency:tree i found logback-core, when I build War the
> lib isn't include.
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Created: (MNG-5139) MAVEN_OPTS are not taked into account in Windows 7
MAVEN_OPTS are not taked into account in Windows 7 -- Key: MNG-5139 URL: https://jira.codehaus.org/browse/MNG-5139 Project: Maven 2 & 3 Issue Type: Bug Components: Command Line Affects Versions: 3.0.3 Environment: Apache Maven 3.0.3 (r1075438; 2011-02-28 14:31:09-0300) Maven home: C:\productos\apache-maven-3.0.3 Java version: 1.6.0_26, vendor: Sun Microsystems Inc. Java home: C:\Program Files\Java\jdk1.6.0_26\jre Default locale: es_AR, platform encoding: Cp1252 OS name: "windows 7", version: "6.1", arch: "x86", family: "windows" Reporter: Gabriel Belingueres Priority: Minor Hi, The mvn.bat file does not take into account the MAVEN_OPTS environment variable, but it does if I add it to the command line (ex. mvn %MAVEN_OPTS%). I fixed it by changing this line of the script: %MAVEN_JAVA_EXE% %MAVEN_OPTS% -classpath %CLASSWORLDS_JAR% "-Dclassworlds.conf=%M2_HOME%\bin\m2.conf" "-Dmaven.home=%M2_HOME%" %CLASSWORLDS_LAUNCHER% %MAVEN_CMD_LINE_ARGS% to this (changed the location of the env var only): %MAVEN_JAVA_EXE% -classpath %CLASSWORLDS_JAR% "-Dclassworlds.conf=%M2_HOME%\bin\m2.conf" "-Dmaven.home=%M2_HOME%" %CLASSWORLDS_LAUNCHER% %MAVEN_OPTS% %MAVEN_CMD_LINE_ARGS% For the record, I used the MAVEN_OPTS variable to pass the http.proxyHost and http.proxyPort to maven, because it seems that the settings.xml is not enough for certaing plugins for checking XML files against its DTDs. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Commented: (MNG-5136) Not all dependency are included in WAR
[ https://jira.codehaus.org/browse/MNG-5136?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=274393#comment-274393 ] luca preziati commented on MNG-5136: I have just tried. Seem work. I think is a problem related to the Windows OS because in MAC, with the same version 1.11 all works. Tomorrow all windows collagues path maven lib and I will retry all system, but in mine, where i fix the lib, currently work well. > Not all dependency are included in WAR > -- > > Key: MNG-5136 > URL: https://jira.codehaus.org/browse/MNG-5136 > Project: Maven 2 & 3 > Issue Type: Bug > Components: General >Affects Versions: 3.0.3 > Environment: Windows Vista 32 Bit, apache maven 3.0.3, java version > "1.6.0_21" > Java(TM) SE Runtime Environment (build 1.6.0_21-b07) > Java HotSpot(TM) Client VM (build 17.0-b17, mixed mode, sharing) >Reporter: luca preziati >Priority: Blocker > Attachments: build-MAVEN-3.0.3.log, build-MAVEN-3.0-SNAPSHOT, Lib > dir.txt, list.txt, tree.TXT > > > When I launch mvn dependency:tree i found logback-core, when I build War the > lib isn't include. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Commented: (MNG-5136) Not all dependency are included in WAR
[ https://jira.codehaus.org/browse/MNG-5136?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=274394#comment-274394 ] luca preziati commented on MNG-5136: Thanks! > Not all dependency are included in WAR > -- > > Key: MNG-5136 > URL: https://jira.codehaus.org/browse/MNG-5136 > Project: Maven 2 & 3 > Issue Type: Bug > Components: General >Affects Versions: 3.0.3 > Environment: Windows Vista 32 Bit, apache maven 3.0.3, java version > "1.6.0_21" > Java(TM) SE Runtime Environment (build 1.6.0_21-b07) > Java HotSpot(TM) Client VM (build 17.0-b17, mixed mode, sharing) >Reporter: luca preziati >Priority: Blocker > Attachments: build-MAVEN-3.0.3.log, build-MAVEN-3.0-SNAPSHOT, Lib > dir.txt, list.txt, tree.TXT > > > When I launch mvn dependency:tree i found logback-core, when I build War the > lib isn't include. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Closed: (MECLIPSE-436) Plugin configuration is not inherited/merged correctly
[
https://jira.codehaus.org/browse/MECLIPSE-436?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Robert Scholte closed MECLIPSE-436.
---
Resolution: Not A Bug
Assignee: Robert Scholte
Please read
http://www.sonatype.com/people/2011/01/maven-how-to-merging-plugin-configuration-in-complex-projects/
and you'll understand what's going on.
> Plugin configuration is not inherited/merged correctly
> --
>
> Key: MECLIPSE-436
> URL: https://jira.codehaus.org/browse/MECLIPSE-436
> Project: Maven 2.x Eclipse Plugin
> Issue Type: Bug
>Affects Versions: 2.5.1
> Environment: mvn 2.0.8
>Reporter: Andreas Höhmann
>Assignee: Robert Scholte
>Priority: Critical
>
> I don't know if this is a maven problem or a plugin-problem:
> Parent-pom:
> ...
>
> true
> maven-eclipse-plugin
>
> [artifactId]
> true
> true
> true
> true
> 2.0
>
> ${basedir}/src/main/resources/META-INF/MANIFEST.MF
>
>
> com.atlassw.tools.eclipse.checkstyle.CheckstyleNature
>
> org.springframework.ide.eclipse.core.springnature
>
> edu.umd.cs.findbugs.plugin.eclipse.findbugsNature
>
>
>
> com.atlassw.tools.eclipse.checkstyle.CheckstyleBuilder
>
> org.springframework.ide.eclipse.core.springbuilder
>
> edu.umd.cs.findbugs.plugin.eclipse.findbugsBuilder
>
>
>
> .checkstyle
> checkstyle/checkstyle.xml
>
>
>
> .settings/org.springframework.ide.eclipse.core.prefs
>
>
>
>
>
>
>
> ...
> If i run mvn eclipse:clean eclipse:eclipse in the subproject ... only the
> .springBeans file will be created.
> If i remove the plugin from the subproject-pom only the .checkstyle, .fbprefs
> will be created but NO .springBeans.
> I would like to merge parent-configuration with sub-project-configuration.
> Is this possible?
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Commented: (MSHARED-167) dependency:tree omits batik-js
[
https://jira.codehaus.org/browse/MSHARED-167?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=274422#comment-274422
]
Jesse Glick commented on MSHARED-167:
-
Possibly related to MNG-4982?
> dependency:tree omits batik-js
> --
>
> Key: MSHARED-167
> URL: https://jira.codehaus.org/browse/MSHARED-167
> Project: Maven Shared Components
> Issue Type: Bug
> Components: maven-dependency-tree
>Affects Versions: maven-dependency-tree-1.2
> Environment: Maven 3.0, Ubuntu, JDK 6.
>Reporter: Jesse Glick
> Attachments:
> test_test-dependency-tree_jar_1.0-SNAPSHOT_101018-185145.zip
>
>
> (Not sure what the right place to file this is. {{maven-dependency-tree 1.2}}
> gives {{MNG}} as the JIRA component by inheritance.)
> {{mvn dependency:tree}} on the attached project lists {{batik-script}} by way
> of {{batik-bridge}} as expected, but then fails to show {{batik-js}} as a
> dependency of that. If you list {{batik-script}} as a direct dependency,
> {{batik-js}} is correctly shown.
> Possibly related is that Maven 2.2.1 also fails to find {{batik-js}} in
> {{MavenProject.getRuntimeArtifacts}}, so {{clean package}} fails, whereas
> this works fine under Maven 3.0. Yet just running the dependency plugin under
> M3 does not suffice to pick up this fix, wherever it was - MNG-4690?
> Although the Batik JARs are built from an odd source tree, the artifacts as
> present in the local repository look normal enough; all of the dependencies
> involved are simple compile scope without exclusions etc.
> Marking "major" since this seems to cause MNBMODULE-102 (producing build
> errors for certain projects); also I have noticed that the dependency graph
> feature in the NB IDE omits {{batik-js}}, and there may be other user-visible
> effects of this bug.
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Created: (MECLIPSE-692) .project contains projects which were skipped during reactor build
.project contains projects which were skipped during reactor build
--
Key: MECLIPSE-692
URL: https://jira.codehaus.org/browse/MECLIPSE-692
Project: Maven 2.x Eclipse Plugin
Issue Type: Bug
Components: Core : .project
Affects Versions: 2.8
Reporter: Robert Scholte
Suppose project A is of type '{{pom}}' and only holds a number of dependencies.
Eclipse won't generate a {{.project}} file for such projects.
Project B has a reference to project A. It will check it is part of the
reactorBuild (it does) so it adds it as a project.
The plugin should also check if such a reference is a valid eclipse-project.
The easiest and most solid way it to check if the {{.project}} file exists.
The order of the reactorbuild is already solved by Maven, so the plugin can
just use it.
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Closed: (MECLIPSE-692) .project contains projects which were skipped during reactor build
[
https://jira.codehaus.org/browse/MECLIPSE-692?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Robert Scholte closed MECLIPSE-692.
---
Resolution: Fixed
Fix Version/s: 2.9
Assignee: Robert Scholte
Fixed in [rev. 1151629|http://svn.apache.org/viewvc?rev=1151629&view=rev]
> .project contains projects which were skipped during reactor build
> --
>
> Key: MECLIPSE-692
> URL: https://jira.codehaus.org/browse/MECLIPSE-692
> Project: Maven 2.x Eclipse Plugin
> Issue Type: Bug
> Components: Core : .project
>Affects Versions: 2.8
>Reporter: Robert Scholte
>Assignee: Robert Scholte
> Fix For: 2.9
>
>
> Suppose project A is of type '{{pom}}' and only holds a number of
> dependencies.
> Eclipse won't generate a {{.project}} file for such projects.
> Project B has a reference to project A. It will check it is part of the
> reactorBuild (it does) so it adds it as a project.
> The plugin should also check if such a reference is a valid eclipse-project.
> The easiest and most solid way it to check if the {{.project}} file exists.
> The order of the reactorbuild is already solved by Maven, so the plugin can
> just use it.
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Updated: (MECLIPSE-586) Using -Declipse.projectNameTemplate is broken on multi module projects
[ https://jira.codehaus.org/browse/MECLIPSE-586?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Robert Scholte updated MECLIPSE-586: Description: In version 2.5.1 when specifying projectNameTemplate on the commandline, the .project file and references are generated correcly. In 2.6 and 2.7 the project has the correct name, but referenced projects is not using the specified pattern. This renderes the .project-file and .classpath useless. Example (using mvn eclipse:eclipse -Declipse.projectNameTemplate=trunk-[artifactId]) where moduleA depends on moduleB: moduleA/.project trunk-moduleA moduleB [..] moduleA/.classpath [..] moduleB/.project trunk-moduleB [..] was: In version 2.5.1 when specifying projectNameTemplate on the commandline, the .project file and references are generated correcly. In 2.6 and 2.7 the project has the correct name, but referenced projects is not using the specified pattern. This renderes the .project-file and .classpath useless. Example (using mvn eclipse:eclipse -Declipse.projectNameTemplate=trunk-[artifactId]) where moduleA depends on moduleB: moduleA/.project trunk-moduleA moduleB [..] moduleA/.classpath [..] moduleB/.project trunk-moduleB [..] Adjusting description according to first comment. > Using -Declipse.projectNameTemplate is broken on multi module projects > -- > > Key: MECLIPSE-586 > URL: https://jira.codehaus.org/browse/MECLIPSE-586 > Project: Maven 2.x Eclipse Plugin > Issue Type: Bug > Components: Core : .project, Core : Dependencies resolution and > build path (.classpath), Core : Multi-projects >Affects Versions: 2.6, 2.7 > Environment: Maven version: 2.0.9 > Java version: 1.6.0_10-rc > OS name: "linux" version: "2.6.27-14-generic" arch: "amd64" Family: "unix" >Reporter: Baard Johansen > > In version 2.5.1 when specifying projectNameTemplate on the commandline, the > .project file and references are generated correcly. In 2.6 and 2.7 the > project has the correct name, but referenced projects is not using the > specified pattern. This renderes the .project-file and .classpath useless. > Example (using mvn eclipse:eclipse > -Declipse.projectNameTemplate=trunk-[artifactId]) where moduleA depends on > moduleB: > moduleA/.project > > trunk-moduleA > > moduleB > > [..] > > moduleA/.classpath > > [..] > > > moduleB/.project > > trunk-moduleB > [..] > -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Created: (MNG-5140) wrong reports order inside reportSet
wrong reports order inside reportSet Key: MNG-5140 URL: https://jira.codehaus.org/browse/MNG-5140 Project: Maven 2 & 3 Issue Type: Bug Components: Inheritance and Interpolation, Sites & Reporting Affects Versions: 2.2.1 Reporter: Herve Boutemy sen when working on MSITE-402, order of report plugins is well respected, but not on reports in a reportSet (seen on Maven Project Info Reports Plugin) -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Closed: (MNG-5140) wrong reports order inside reportSet
[ https://jira.codehaus.org/browse/MNG-5140?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Herve Boutemy closed MNG-5140. -- Resolution: Fixed Fix Version/s: 2.2.2 Assignee: Herve Boutemy fixed in [r1151649|http://svn.apache.org/viewvc?rev=1151649&view=rev] > wrong reports order inside reportSet > > > Key: MNG-5140 > URL: https://jira.codehaus.org/browse/MNG-5140 > Project: Maven 2 & 3 > Issue Type: Bug > Components: Inheritance and Interpolation, Sites & Reporting >Affects Versions: 2.2.1 >Reporter: Herve Boutemy >Assignee: Herve Boutemy > Fix For: 2.2.2 > > > sen when working on MSITE-402, order of report plugins is well respected, but > not on reports in a reportSet (seen on Maven Project Info Reports Plugin) -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Commented: (MNG-5086) Maven 3.0.3 fails to use relativePath for parent pom location.
[
https://jira.codehaus.org/browse/MNG-5086?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=274451#comment-274451
]
Ryan J commented on MNG-5086:
-
Just in case anyone else runs into this, here is a modified version of the
original attachment that does a better job of what I was trying to accomplish.
I've been using this type of project layout as a 'workaround' for a few weeks,
but I've found it actually works better than my original configuration.
Benjamin's explanation makes it clear that my original configuration was
broken. The only changes are:
- remove modules from the parent POM
- include the parent POM and all modules in the group POM
I use multiple grouping modules for convenience so I have an easy way to build
part of my project at a time. For example, all of the client side modules vs
all of the server side modules.
In the updated layout, the parent POM is used for dependency and plugin
management. The grouping logic is consolidated within dedicated modules that
can be used optionally. The grouping logic is easier to understand since it's
clearer which modules are going to be built. The parent module is easier to
include as a build configuration on my build server since building every child
module along with it is no longer a requirement.
Hopefully this is useful to anyone trying to solve a similar problem. I
apologize if it's poor etiquette for me to add to closed bug report.
> Maven 3.0.3 fails to use relativePath for parent pom location.
> --
>
> Key: MNG-5086
> URL: https://jira.codehaus.org/browse/MNG-5086
> Project: Maven 2 & 3
> Issue Type: Bug
>Affects Versions: 3.0.3
> Environment: Windows 7
>Reporter: Ryan J
>Assignee: Benjamin Bentmann
> Attachments: maven-dependency-grouping-2.rar,
> maven-dependency-grouping.zip
>
>
> After updating to Maven 3.0.3 I've noticed it fails to use the 'relativePath'
> I've specified in the 'parent' section of my POMs. The
> [documentation|http://maven.apache.org/ref/3.0.3/maven-model/maven.html#class_parent]
> states:
> {quote}
> Maven looks for the parent POM first in this location on the filesystem, then
> the local repository, and lastly in the remote repo.
> {quote}
> However, this does not appear to be the case. I'll attach an example project
> (please excuse the inaccurate name). To reproduce:
> 1) Go to the *group* module and run {{mvn clean install}}
> 2) Go to the *moduleA* module and run {{mvn compile}}
> Step one should install the modules *depends*, *moduleB* and *group* to the
> local repository. The *maven-dependency-grouping* module will _not_ be
> installed to the local repository. At step two, *moduleA* should compile,
> but fails with the (partial) error:
> {quote}
> Could not find artifact
> maven-dependency-grouping:maven-dependency-grouping:pom:0.1-SNAPSHOT in...
> {quote}
> According to the documentation, the above dependency should get resolved via
> the 'relativePath' specified in the 'parent' element of the POM. Maven 2.2.1
> behaves correctly when repeating the above steps.
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Updated: (MNG-5086) Maven 3.0.3 fails to use relativePath for parent pom location.
[
https://jira.codehaus.org/browse/MNG-5086?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Ryan J updated MNG-5086:
Attachment: maven-dependency-grouping-2.rar
Improved project layout.
> Maven 3.0.3 fails to use relativePath for parent pom location.
> --
>
> Key: MNG-5086
> URL: https://jira.codehaus.org/browse/MNG-5086
> Project: Maven 2 & 3
> Issue Type: Bug
>Affects Versions: 3.0.3
> Environment: Windows 7
>Reporter: Ryan J
>Assignee: Benjamin Bentmann
> Attachments: maven-dependency-grouping-2.rar,
> maven-dependency-grouping.zip
>
>
> After updating to Maven 3.0.3 I've noticed it fails to use the 'relativePath'
> I've specified in the 'parent' section of my POMs. The
> [documentation|http://maven.apache.org/ref/3.0.3/maven-model/maven.html#class_parent]
> states:
> {quote}
> Maven looks for the parent POM first in this location on the filesystem, then
> the local repository, and lastly in the remote repo.
> {quote}
> However, this does not appear to be the case. I'll attach an example project
> (please excuse the inaccurate name). To reproduce:
> 1) Go to the *group* module and run {{mvn clean install}}
> 2) Go to the *moduleA* module and run {{mvn compile}}
> Step one should install the modules *depends*, *moduleB* and *group* to the
> local repository. The *maven-dependency-grouping* module will _not_ be
> installed to the local repository. At step two, *moduleA* should compile,
> but fails with the (partial) error:
> {quote}
> Could not find artifact
> maven-dependency-grouping:maven-dependency-grouping:pom:0.1-SNAPSHOT in...
> {quote}
> According to the documentation, the above dependency should get resolved via
> the 'relativePath' specified in the 'parent' element of the POM. Maven 2.2.1
> behaves correctly when repeating the above steps.
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Commented: (MSITE-585) site-deploy: empty deploy protocol when properties are used
[ https://jira.codehaus.org/browse/MSITE-585?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=274457#comment-274457 ] Benson Margulies commented on MSITE-585: I seem to have run into a variation on this theme. Parent has a distributionManagement that has property references. Child completely overrides it: parent.website scp://souvenir.basistech.net:/basis/trees/maven-projects/oap/parent Yet I still get the error, and -X shows that the site plugin is using the value of from the parent, not from the current project. > site-deploy: empty deploy protocol when properties are used > --- > > Key: MSITE-585 > URL: https://jira.codehaus.org/browse/MSITE-585 > Project: Maven 2.x and 3.x Site Plugin > Issue Type: Bug > Components: property interpolation >Affects Versions: 2.3 >Reporter: Lukas Theussl >Assignee: Lukas Theussl > Fix For: 2.4 > > > See http://www.mail-archive.com/dev@maven.apache.org/msg88029.html -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Created: (MRELEASE-697) version 2.2 includes SNAPSHOT in default tag name
version 2.2 includes SNAPSHOT in default tag name
-
Key: MRELEASE-697
URL: https://jira.codehaus.org/browse/MRELEASE-697
Project: Maven 2.x Release Plugin
Issue Type: Bug
Components: prepare
Affects Versions: 2.2
Reporter: Benson Margulies
There's a test case here:
https://svn.apache.org/repos/asf/maven/sandbox/bimargulies/mrp-snap-tc/trunk
2.1 does the expected thing (no -SNAPSHOT in the proposed tag name).
/Users/benson/asf/mvn/mrp-snap-tc /opt/apache-maven-2.2.1/bin/mvn -DdryRun=true
release:prepare
[INFO] Scanning for projects...
[INFO] Searching repository for plugin with prefix: 'release'.
[INFO]
[INFO] Building test case for strange behavior
[INFO]task-segment: [release:prepare] (aggregator-style)
[INFO]
[INFO] [release:prepare {execution: default-cli}]
[INFO] Verifying that there are no local modifications...
[INFO] ignoring changes on: pom.xml.next, release.properties,
pom.xml.releaseBackup, pom.xml.backup, pom.xml.branch, pom.xml.tag
[INFO] Executing: /bin/sh -c cd /Users/benson/asf/mvn/mrp-snap-tc && svn status
[INFO] Working directory: /Users/benson/asf/mvn/mrp-snap-tc
[INFO] Checking dependencies and plugins for snapshots ...
What is the release version for "test case for strange behavior"?
(org.apache.maven:mrp-snap-tag-tc) 1: :
What is SCM release tag or label for "test case for strange behavior"?
(org.apache.maven:mrp-snap-tag-tc) mrp-snap-tag-tc-1-SNAPSHOT: :
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Updated: (MSITE-585) site-deploy: empty deploy protocol when properties are used
[ https://jira.codehaus.org/browse/MSITE-585?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Benson Margulies updated MSITE-585: --- Attachment: muddle.tar Test case which suggests that this might not be all fixed yet. > site-deploy: empty deploy protocol when properties are used > --- > > Key: MSITE-585 > URL: https://jira.codehaus.org/browse/MSITE-585 > Project: Maven 2.x and 3.x Site Plugin > Issue Type: Bug > Components: property interpolation >Affects Versions: 2.3 >Reporter: Lukas Theussl >Assignee: Lukas Theussl > Fix For: 2.4 > > Attachments: muddle.tar > > > See http://www.mail-archive.com/dev@maven.apache.org/msg88029.html -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Commented: (MSITE-585) site-deploy: empty deploy protocol when properties are used
[ https://jira.codehaus.org/browse/MSITE-585?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=274464#comment-274464 ] Benson Margulies commented on MSITE-585: OK, the test case I attached 'works' for 2.4-SNAPSHOT, but exhibits another problem I'll report separately. > site-deploy: empty deploy protocol when properties are used > --- > > Key: MSITE-585 > URL: https://jira.codehaus.org/browse/MSITE-585 > Project: Maven 2.x and 3.x Site Plugin > Issue Type: Bug > Components: property interpolation >Affects Versions: 2.3 >Reporter: Lukas Theussl >Assignee: Lukas Theussl > Fix For: 2.4 > > Attachments: muddle.tar > > > See http://www.mail-archive.com/dev@maven.apache.org/msg88029.html -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Created: (MSITE-600) site plugin 2.4 does not permit a child to fully override parent site deployment URL
site plugin 2.4 does not permit a child to fully override parent site deployment URL Key: MSITE-600 URL: https://jira.codehaus.org/browse/MSITE-600 Project: Maven 2.x and 3.x Site Plugin Issue Type: Bug Components: site:deploy Affects Versions: 2.4 Reporter: Benson Margulies Attachments: muddle.tar The test cases here has a parent with a a distributionManagement/site/url, and then a child which overrides it with an absolute URL. Except that the override does not work ... or, at least, looks quite peculiar. the parent is file:///tmp/bloop the child is scp://localhost:/tmp/blop and the result is [INFO] Error uploading site Embedded error: Could not make directory '/tmp/bloop/../../Users/benson/asf/mvn/site-interp-muddle/child/scp:/localhost:/tmp/blop'. [INFO] --- -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Issue Comment Edited: (MSITE-600) site plugin 2.4 does not permit a child to fully override parent site deployment URL
[ https://jira.codehaus.org/browse/MSITE-600?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=274465#comment-274465 ] Benson Margulies edited comment on MSITE-600 at 7/27/11 11:36 PM: -- This is all testing with maven 2.2.1. was (Author: bmargulies): This is all testing with maven 2.2.0. > site plugin 2.4 does not permit a child to fully override parent site > deployment URL > > > Key: MSITE-600 > URL: https://jira.codehaus.org/browse/MSITE-600 > Project: Maven 2.x and 3.x Site Plugin > Issue Type: Bug > Components: site:deploy >Affects Versions: 2.4 >Reporter: Benson Margulies > Attachments: muddle.tar > > > The test cases here has a parent with a a distributionManagement/site/url, > and then a child which overrides it with an absolute URL. Except that the > override does not work ... or, at least, looks quite peculiar. > the parent is file:///tmp/bloop > the child is scp://localhost:/tmp/blop > and the result is > [INFO] Error uploading site > Embedded error: Could not make directory > '/tmp/bloop/../../Users/benson/asf/mvn/site-interp-muddle/child/scp:/localhost:/tmp/blop'. > [INFO] --- -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Commented: (MSITE-600) site plugin 2.4 does not permit a child to fully override parent site deployment URL
[ https://jira.codehaus.org/browse/MSITE-600?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=274465#comment-274465 ] Benson Margulies commented on MSITE-600: This is all testing with maven 2.2.0. > site plugin 2.4 does not permit a child to fully override parent site > deployment URL > > > Key: MSITE-600 > URL: https://jira.codehaus.org/browse/MSITE-600 > Project: Maven 2.x and 3.x Site Plugin > Issue Type: Bug > Components: site:deploy >Affects Versions: 2.4 >Reporter: Benson Margulies > Attachments: muddle.tar > > > The test cases here has a parent with a a distributionManagement/site/url, > and then a child which overrides it with an absolute URL. Except that the > override does not work ... or, at least, looks quite peculiar. > the parent is file:///tmp/bloop > the child is scp://localhost:/tmp/blop > and the result is > [INFO] Error uploading site > Embedded error: Could not make directory > '/tmp/bloop/../../Users/benson/asf/mvn/site-interp-muddle/child/scp:/localhost:/tmp/blop'. > [INFO] --- -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Commented: (MSITE-600) site plugin 2.4 does not permit a child to fully override parent site deployment URL
[ https://jira.codehaus.org/browse/MSITE-600?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=274466#comment-274466 ] Benson Margulies commented on MSITE-600: To run this just go to the child directory and run mvn site-deploy. > site plugin 2.4 does not permit a child to fully override parent site > deployment URL > > > Key: MSITE-600 > URL: https://jira.codehaus.org/browse/MSITE-600 > Project: Maven 2.x and 3.x Site Plugin > Issue Type: Bug > Components: site:deploy >Affects Versions: 2.4 >Reporter: Benson Margulies > Attachments: muddle.tar > > > The test cases here has a parent with a a distributionManagement/site/url, > and then a child which overrides it with an absolute URL. Except that the > override does not work ... or, at least, looks quite peculiar. > the parent is file:///tmp/bloop > the child is scp://localhost:/tmp/blop > and the result is > [INFO] Error uploading site > Embedded error: Could not make directory > '/tmp/bloop/../../Users/benson/asf/mvn/site-interp-muddle/child/scp:/localhost:/tmp/blop'. > [INFO] --- -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Commented: (MSITE-600) site plugin 2.4 does not permit a child to fully override parent site deployment URL
[ https://jira.codehaus.org/browse/MSITE-600?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=274473#comment-274473 ] Lukas Theussl commented on MSITE-600: - Is this a realistic use case? Why would you want to deploy the child to a different host? I think that currently it is assumed that related sites (modules, parent) are deployed to the same host, otherwise e.g. relative links between components will not work. > site plugin 2.4 does not permit a child to fully override parent site > deployment URL > > > Key: MSITE-600 > URL: https://jira.codehaus.org/browse/MSITE-600 > Project: Maven 2.x and 3.x Site Plugin > Issue Type: Bug > Components: site:deploy >Affects Versions: 2.4 >Reporter: Benson Margulies > Attachments: muddle.tar > > > The test cases here has a parent with a a distributionManagement/site/url, > and then a child which overrides it with an absolute URL. Except that the > override does not work ... or, at least, looks quite peculiar. > the parent is file:///tmp/bloop > the child is scp://localhost:/tmp/blop > and the result is > [INFO] Error uploading site > Embedded error: Could not make directory > '/tmp/bloop/../../Users/benson/asf/mvn/site-interp-muddle/child/scp:/localhost:/tmp/blop'. > [INFO] --- -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira
