[jira] Closed: (MNG-4361) [regression] command line option "-update-snapshots" does not work
[
http://jira.codehaus.org/browse/MNG-4361?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Benjamin Bentmann closed MNG-4361.
--
Assignee: Benjamin Bentmann
Resolution: Fixed
Fix Version/s: 3.0-alpha-3
Fixed in [r816002|http://svn.apache.org/viewvc?view=rev&revision=816002].
> [regression] command line option "-update-snapshots" does not work
> --
>
> Key: MNG-4361
> URL: http://jira.codehaus.org/browse/MNG-4361
> Project: Maven 2
> Issue Type: Bug
> Components: Artifacts and Repositories
>Affects Versions: 3.0-alpha-3
>Reporter: Benjamin Bentmann
>Assignee: Benjamin Bentmann
> Fix For: 3.0-alpha-3
>
>
> "mvn package -U" is not checking for updated snapshots on trunk and the debug
> log reveals
> {noformat]
> [DEBUG] Skipping metadata update of snapshot ...
> {noformat]
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://jira.codehaus.org/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Reopened: (MRELEASE-461) Add a mojo parameter for using the new remote tagging for svn scm provider (to prevent issue with svn > 1.5.0) in branch mojo
[ http://jira.codehaus.org/browse/MRELEASE-461?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Olivier Lamy reopened MRELEASE-461: --- reopen due to user comment. > Add a mojo parameter for using the new remote tagging for svn scm provider > (to prevent issue with svn > 1.5.0) in branch mojo > - > > Key: MRELEASE-461 > URL: http://jira.codehaus.org/browse/MRELEASE-461 > Project: Maven 2.x Release Plugin > Issue Type: Improvement > Components: scm >Affects Versions: 2.0-beta-9 >Reporter: Orestes Garcia >Assignee: Olivier Lamy >Priority: Critical > Fix For: 2.0-beta-10 > > > Due to an issue with svn > 1.5.0, release plugin doesn't work. The scm (1.2) > implements a new remote tagging mechanism as a workaround. > This is fixed for release:prepare in MRELEASE-427 > I have the same problem when executing mvn release:branch. > It would be useful to add the -DremoteTagging argument also when making > branches. > Thank you. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Commented: (MRELEASE-461) Add a mojo parameter for using the new remote tagging for svn scm provider (to prevent issue with svn > 1.5.0) in branch mojo
[ http://jira.codehaus.org/browse/MRELEASE-461?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=191188#action_191188 ] Benson Margulies commented on MRELEASE-461: --- The current snapshot does not work. If the snapshot is stale, please publish a new one. If it is not, please reopen. Provider message: The svn branch command failed. Command output: svn: Commit failed (details follow): svn: File '/engineering/rex2009/branches/rlp-7.0/ama/pom.xml' already exists > Add a mojo parameter for using the new remote tagging for svn scm provider > (to prevent issue with svn > 1.5.0) in branch mojo > - > > Key: MRELEASE-461 > URL: http://jira.codehaus.org/browse/MRELEASE-461 > Project: Maven 2.x Release Plugin > Issue Type: Improvement > Components: scm >Affects Versions: 2.0-beta-9 >Reporter: Orestes Garcia >Assignee: Olivier Lamy >Priority: Critical > Fix For: 2.0-beta-10 > > > Due to an issue with svn > 1.5.0, release plugin doesn't work. The scm (1.2) > implements a new remote tagging mechanism as a workaround. > This is fixed for release:prepare in MRELEASE-427 > I have the same problem when executing mvn release:branch. > It would be useful to add the -DremoteTagging argument also when making > branches. > Thank you. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Created: (MRELEASE-484) release:rollback fails after branch with NPE and complaint about missing scm URL
release:rollback fails after branch with NPE and complaint about missing scm URL Key: MRELEASE-484 URL: http://jira.codehaus.org/browse/MRELEASE-484 Project: Maven 2.x Release Plugin Issue Type: Bug Components: branch Affects Versions: 2.0-beta-9 Reporter: Benson Margulies After a problem with release:branch (possibly the 'remoteTagging' problem) an attempt to run rollback got me the following. The SCM urls are indeed in the POM. [INFO] Trace java.lang.NullPointerException: The scm url cannot be null. at org.apache.maven.scm.manager.AbstractScmManager.makeScmRepository(AbstractScmManager.java:181) at org.apache.maven.shared.release.scm.DefaultScmRepositoryConfigurator.getConfiguredRepository(DefaultScmRepositoryConfigurator.java:62) at org.apache.maven.shared.release.phase.RestoreBackupPomsPhase.restorePomBackup(RestoreBackupPomsPhase.java:100) at org.apache.maven.shared.release.phase.RestoreBackupPomsPhase.execute(RestoreBackupPomsPhase.java:69) at org.apache.maven.shared.release.DefaultReleaseManager.rollback(DefaultReleaseManager.java:250) at org.apache.maven.shared.release.DefaultReleaseManager.rollback(DefaultReleaseManager.java:227) at org.apache.maven.plugins.release.RollbackReleaseMojo.execute(RollbackReleaseMojo.java:54) at org.apache.maven.plugin.DefaultPluginManager.executeMojo(DefaultPluginManager.java:483) at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoals(DefaultLifecycleExecutor.java:678) at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeStandaloneGoal(DefaultLifecycleExecutor.java:553) at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoal(DefaultLifecycleExecutor.java:523) at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoalAndHandleFailures(DefaultLifecycleExecutor.java:371) at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeTaskSegments(DefaultLifecycleExecutor.java:268) at org.apache.maven.lifecycle.DefaultLifecycleExecutor.execute(DefaultLifecycleExecutor.java:181) at org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:356) at org.apache.maven.DefaultMaven.execute(DefaultMaven.java:137) at org.apache.maven.cli.MavenCli.main(MavenCli.java:356) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) at java.lang.reflect.Method.invoke(Method.java:597) at org.codehaus.classworlds.Launcher.launchEnhanced(Launcher.java:315) at org.codehaus.classworlds.Launcher.launch(Launcher.java:255) at org.codehaus.classworlds.Launcher.mainWithExitCode(Launcher.java:430) at org.codehaus.classworlds.Launcher.main(Launcher.java:375) [INFO] -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Commented: (MRELEASE-248) release:prepare fails with Starteam 2006
[ http://jira.codehaus.org/browse/MRELEASE-248?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=191182#action_191182 ] Fábio Lima Santos commented on MRELEASE-248: On StartTeam 2006, using the option "-o" on the command line (as the example bellow) we managed to manually checkin the file. stcmd ci -x -nologo -stop -p gu...@foo:49213/Maven/1.2/project -fp D:/temp/1.2/project -r "[maven-release-plugin] prepare release foo-1.2.0" -eol on -o pom.xml We also have to insert manually the view identifier in order to upload the file to the correct branch. It has been a while this issue is opened. Are there any workarounds on the way? > release:prepare fails with Starteam 2006 > > > Key: MRELEASE-248 > URL: http://jira.codehaus.org/browse/MRELEASE-248 > Project: Maven 2.x Release Plugin > Issue Type: Bug > Components: prepare >Affects Versions: 2.0-beta-6 > Environment: windows xp, starteam 2006 >Reporter: Giovanni Pedone > > when performing release:prepare and issuing the command stcmd, it fails to > checkout/checkin, complaining about "Unknown status". > It does not happen with stcmd shipping with Starteam 2005 R2. > It happens only with Starteam 2006 stcmd. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Created: (MNG-4361) [regression] command line option "-update-snapshots" does not work
[regression] command line option "-update-snapshots" does not work
--
Key: MNG-4361
URL: http://jira.codehaus.org/browse/MNG-4361
Project: Maven 2
Issue Type: Bug
Components: Artifacts and Repositories
Affects Versions: 3.0-alpha-3
Reporter: Benjamin Bentmann
"mvn package -U" is not checking for updated snapshots on trunk and the debug
log reveals
{noformat]
[DEBUG] Skipping metadata update of snapshot ...
{noformat]
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://jira.codehaus.org/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Created: (MAVENUPLOAD-2603) Upload information in comma delimited format
Upload information in comma delimited format Key: MAVENUPLOAD-2603 URL: http://jira.codehaus.org/browse/MAVENUPLOAD-2603 Project: Maven Upload Requests Issue Type: Wish Reporter: Adrian Kuhn "ch.unibe.jexample","ma...@haddock.unibe.ch:/home/scg/download/jexample/maven","rsync_ssh","Adrian Kuhn","ak...@iam.unibe.com",, -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Issue Comment Edited: (MINSTALL-70) install-file should take the version from the parent if the version for the artifact is missing in the POM
[
http://jira.codehaus.org/browse/MINSTALL-70?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=191173#action_191173
]
Benjamin Bentmann edited comment on MINSTALL-70 at 9/16/09 10:16 AM:
-
That's not what I asked for. You either need to tell the Maven version being
used or attach the output of "mvn install:install-file ... > debug.log".
Or, just try {{mvn
org.apache.maven.plugins:maven-install-plugin:2.3:install-file ...}}, i.e.
explicitly select the version that is known to work.
was (Author: bentmann):
That's not what I asked for. You either need to tell the Maven version
being used or attach the output of "mvn install:install-file ... > debug.log".
> install-file should take the version from the parent if the version for the
> artifact is missing in the POM
> --
>
> Key: MINSTALL-70
> URL: http://jira.codehaus.org/browse/MINSTALL-70
> Project: Maven 2.x Install Plugin
> Issue Type: Bug
> Components: install:install-file
>Affects Versions: 2.2
>Reporter: Eric Lewis
>
> Spring Source seems to release POM which have no version. According to the
> Maven philosophy this means that they inherit their parent's version.
> However, if I try
> {{mvn install:install-file -Dfile=spring-ldap-core-1.3.0.RELEASE.jar
> -DpomFile=pom.xml}}
> I get
> {quote}
> [INFO] Scanning for projects...
> [INFO] Searching repository for plugin with prefix: 'install'.
> [INFO]
>
> [INFO] Building Spring LDAP Core
> [INFO]task-segment: [install:install-file] (aggregator-style)
> [INFO]
>
> [INFO] [install:install-file {execution: default-cli}]
> [INFO]
>
> [ERROR] FATAL ERROR
> [INFO]
>
> [INFO] An invalid artifact was detected.
> This artifact might be in your project's POM, or it might have been included
> transitively during the resolution process. Here is the information we do
> have for this artifact:
> o GroupID: org.springframework.ldap
> o ArtifactID: spring-ldap-core
> o Version: <<< MISSING >>>
> o Type:pom
> [INFO]
>
> [INFO] Trace
> org.apache.maven.artifact.InvalidArtifactRTException: For artifact
> {org.springframework.ldap:spring-ldap-core:null:pom}: The version cannot be
> empty.
> {quote}
> The POM looks like this:
> {quote}
>
> xmlns="http://maven.apache.org/POM/4.0.0";
> xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance";
> xsi:schemaLocation="http://maven.apache.org/POM/4.0.0
> http://maven.apache.org/maven-v4_0_0.xsd";>
>
> org.springframework.ldap
> spring-ldap-parent
> 1.3.0.RELEASE
>
> 4.0.0
> spring-ldap-core
> jar
> Spring LDAP Core
>
> ...
> {quote}
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://jira.codehaus.org/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Closed: (MINSTALL-70) install-file should take the version from the parent if the version for the artifact is missing in the POM
[
http://jira.codehaus.org/browse/MINSTALL-70?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Benjamin Bentmann closed MINSTALL-70.
-
Assignee: Benjamin Bentmann
Resolution: Duplicate
Fix Version/s: (was: 2.3)
> install-file should take the version from the parent if the version for the
> artifact is missing in the POM
> --
>
> Key: MINSTALL-70
> URL: http://jira.codehaus.org/browse/MINSTALL-70
> Project: Maven 2.x Install Plugin
> Issue Type: Bug
> Components: install:install-file
>Affects Versions: 2.2
>Reporter: Eric Lewis
>Assignee: Benjamin Bentmann
>
> Spring Source seems to release POM which have no version. According to the
> Maven philosophy this means that they inherit their parent's version.
> However, if I try
> {{mvn install:install-file -Dfile=spring-ldap-core-1.3.0.RELEASE.jar
> -DpomFile=pom.xml}}
> I get
> {quote}
> [INFO] Scanning for projects...
> [INFO] Searching repository for plugin with prefix: 'install'.
> [INFO]
>
> [INFO] Building Spring LDAP Core
> [INFO]task-segment: [install:install-file] (aggregator-style)
> [INFO]
>
> [INFO] [install:install-file {execution: default-cli}]
> [INFO]
>
> [ERROR] FATAL ERROR
> [INFO]
>
> [INFO] An invalid artifact was detected.
> This artifact might be in your project's POM, or it might have been included
> transitively during the resolution process. Here is the information we do
> have for this artifact:
> o GroupID: org.springframework.ldap
> o ArtifactID: spring-ldap-core
> o Version: <<< MISSING >>>
> o Type:pom
> [INFO]
>
> [INFO] Trace
> org.apache.maven.artifact.InvalidArtifactRTException: For artifact
> {org.springframework.ldap:spring-ldap-core:null:pom}: The version cannot be
> empty.
> {quote}
> The POM looks like this:
> {quote}
>
> xmlns="http://maven.apache.org/POM/4.0.0";
> xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance";
> xsi:schemaLocation="http://maven.apache.org/POM/4.0.0
> http://maven.apache.org/maven-v4_0_0.xsd";>
>
> org.springframework.ldap
> spring-ldap-parent
> 1.3.0.RELEASE
>
> 4.0.0
> spring-ldap-core
> jar
> Spring LDAP Core
>
> ...
> {quote}
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://jira.codehaus.org/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Updated: (MINSTALL-70) install-file should take the version from the parent if the version for the artifact is missing in the POM
[
http://jira.codehaus.org/browse/MINSTALL-70?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Benjamin Bentmann updated MINSTALL-70:
--
Affects Version/s: (was: 2.3)
2.2
> install-file should take the version from the parent if the version for the
> artifact is missing in the POM
> --
>
> Key: MINSTALL-70
> URL: http://jira.codehaus.org/browse/MINSTALL-70
> Project: Maven 2.x Install Plugin
> Issue Type: Bug
> Components: install:install-file
>Affects Versions: 2.2
>Reporter: Eric Lewis
>
> Spring Source seems to release POM which have no version. According to the
> Maven philosophy this means that they inherit their parent's version.
> However, if I try
> {{mvn install:install-file -Dfile=spring-ldap-core-1.3.0.RELEASE.jar
> -DpomFile=pom.xml}}
> I get
> {quote}
> [INFO] Scanning for projects...
> [INFO] Searching repository for plugin with prefix: 'install'.
> [INFO]
>
> [INFO] Building Spring LDAP Core
> [INFO]task-segment: [install:install-file] (aggregator-style)
> [INFO]
>
> [INFO] [install:install-file {execution: default-cli}]
> [INFO]
>
> [ERROR] FATAL ERROR
> [INFO]
>
> [INFO] An invalid artifact was detected.
> This artifact might be in your project's POM, or it might have been included
> transitively during the resolution process. Here is the information we do
> have for this artifact:
> o GroupID: org.springframework.ldap
> o ArtifactID: spring-ldap-core
> o Version: <<< MISSING >>>
> o Type:pom
> [INFO]
>
> [INFO] Trace
> org.apache.maven.artifact.InvalidArtifactRTException: For artifact
> {org.springframework.ldap:spring-ldap-core:null:pom}: The version cannot be
> empty.
> {quote}
> The POM looks like this:
> {quote}
>
> xmlns="http://maven.apache.org/POM/4.0.0";
> xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance";
> xsi:schemaLocation="http://maven.apache.org/POM/4.0.0
> http://maven.apache.org/maven-v4_0_0.xsd";>
>
> org.springframework.ldap
> spring-ldap-parent
> 1.3.0.RELEASE
>
> 4.0.0
> spring-ldap-core
> jar
> Spring LDAP Core
>
> ...
> {quote}
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://jira.codehaus.org/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Reopened: (MINSTALL-70) install-file should take the version from the parent if the version for the artifact is missing in the POM
[
http://jira.codehaus.org/browse/MINSTALL-70?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Benjamin Bentmann reopened MINSTALL-70:
---
> install-file should take the version from the parent if the version for the
> artifact is missing in the POM
> --
>
> Key: MINSTALL-70
> URL: http://jira.codehaus.org/browse/MINSTALL-70
> Project: Maven 2.x Install Plugin
> Issue Type: Bug
> Components: install:install-file
>Affects Versions: 2.2
>Reporter: Eric Lewis
>
> Spring Source seems to release POM which have no version. According to the
> Maven philosophy this means that they inherit their parent's version.
> However, if I try
> {{mvn install:install-file -Dfile=spring-ldap-core-1.3.0.RELEASE.jar
> -DpomFile=pom.xml}}
> I get
> {quote}
> [INFO] Scanning for projects...
> [INFO] Searching repository for plugin with prefix: 'install'.
> [INFO]
>
> [INFO] Building Spring LDAP Core
> [INFO]task-segment: [install:install-file] (aggregator-style)
> [INFO]
>
> [INFO] [install:install-file {execution: default-cli}]
> [INFO]
>
> [ERROR] FATAL ERROR
> [INFO]
>
> [INFO] An invalid artifact was detected.
> This artifact might be in your project's POM, or it might have been included
> transitively during the resolution process. Here is the information we do
> have for this artifact:
> o GroupID: org.springframework.ldap
> o ArtifactID: spring-ldap-core
> o Version: <<< MISSING >>>
> o Type:pom
> [INFO]
>
> [INFO] Trace
> org.apache.maven.artifact.InvalidArtifactRTException: For artifact
> {org.springframework.ldap:spring-ldap-core:null:pom}: The version cannot be
> empty.
> {quote}
> The POM looks like this:
> {quote}
>
> xmlns="http://maven.apache.org/POM/4.0.0";
> xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance";
> xsi:schemaLocation="http://maven.apache.org/POM/4.0.0
> http://maven.apache.org/maven-v4_0_0.xsd";>
>
> org.springframework.ldap
> spring-ldap-parent
> 1.3.0.RELEASE
>
> 4.0.0
> spring-ldap-core
> jar
> Spring LDAP Core
>
> ...
> {quote}
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://jira.codehaus.org/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Closed: (MINSTALL-70) install-file should take the version from the parent if the version for the artifact is missing in the POM
[
http://jira.codehaus.org/browse/MINSTALL-70?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Eric Lewis closed MINSTALL-70.
--
Resolution: Fixed
Fix Version/s: 2.3
Sorry for that! I was using 2.2 without knowing.
> install-file should take the version from the parent if the version for the
> artifact is missing in the POM
> --
>
> Key: MINSTALL-70
> URL: http://jira.codehaus.org/browse/MINSTALL-70
> Project: Maven 2.x Install Plugin
> Issue Type: Bug
> Components: install:install-file
>Affects Versions: 2.3
>Reporter: Eric Lewis
> Fix For: 2.3
>
>
> Spring Source seems to release POM which have no version. According to the
> Maven philosophy this means that they inherit their parent's version.
> However, if I try
> {{mvn install:install-file -Dfile=spring-ldap-core-1.3.0.RELEASE.jar
> -DpomFile=pom.xml}}
> I get
> {quote}
> [INFO] Scanning for projects...
> [INFO] Searching repository for plugin with prefix: 'install'.
> [INFO]
>
> [INFO] Building Spring LDAP Core
> [INFO]task-segment: [install:install-file] (aggregator-style)
> [INFO]
>
> [INFO] [install:install-file {execution: default-cli}]
> [INFO]
>
> [ERROR] FATAL ERROR
> [INFO]
>
> [INFO] An invalid artifact was detected.
> This artifact might be in your project's POM, or it might have been included
> transitively during the resolution process. Here is the information we do
> have for this artifact:
> o GroupID: org.springframework.ldap
> o ArtifactID: spring-ldap-core
> o Version: <<< MISSING >>>
> o Type:pom
> [INFO]
>
> [INFO] Trace
> org.apache.maven.artifact.InvalidArtifactRTException: For artifact
> {org.springframework.ldap:spring-ldap-core:null:pom}: The version cannot be
> empty.
> {quote}
> The POM looks like this:
> {quote}
>
> xmlns="http://maven.apache.org/POM/4.0.0";
> xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance";
> xsi:schemaLocation="http://maven.apache.org/POM/4.0.0
> http://maven.apache.org/maven-v4_0_0.xsd";>
>
> org.springframework.ldap
> spring-ldap-parent
> 1.3.0.RELEASE
>
> 4.0.0
> spring-ldap-core
> jar
> Spring LDAP Core
>
> ...
> {quote}
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://jira.codehaus.org/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Commented: (MINSTALL-70) install-file should take the version from the parent if the version for the artifact is missing in the POM
[
http://jira.codehaus.org/browse/MINSTALL-70?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=191173#action_191173
]
Benjamin Bentmann commented on MINSTALL-70:
---
That's not what I asked for. You either need to tell the Maven version being
used or attach the output of "mvn install:install-file ... > debug.log".
> install-file should take the version from the parent if the version for the
> artifact is missing in the POM
> --
>
> Key: MINSTALL-70
> URL: http://jira.codehaus.org/browse/MINSTALL-70
> Project: Maven 2.x Install Plugin
> Issue Type: Bug
> Components: install:install-file
>Affects Versions: 2.3
>Reporter: Eric Lewis
> Fix For: 2.3
>
>
> Spring Source seems to release POM which have no version. According to the
> Maven philosophy this means that they inherit their parent's version.
> However, if I try
> {{mvn install:install-file -Dfile=spring-ldap-core-1.3.0.RELEASE.jar
> -DpomFile=pom.xml}}
> I get
> {quote}
> [INFO] Scanning for projects...
> [INFO] Searching repository for plugin with prefix: 'install'.
> [INFO]
>
> [INFO] Building Spring LDAP Core
> [INFO]task-segment: [install:install-file] (aggregator-style)
> [INFO]
>
> [INFO] [install:install-file {execution: default-cli}]
> [INFO]
>
> [ERROR] FATAL ERROR
> [INFO]
>
> [INFO] An invalid artifact was detected.
> This artifact might be in your project's POM, or it might have been included
> transitively during the resolution process. Here is the information we do
> have for this artifact:
> o GroupID: org.springframework.ldap
> o ArtifactID: spring-ldap-core
> o Version: <<< MISSING >>>
> o Type:pom
> [INFO]
>
> [INFO] Trace
> org.apache.maven.artifact.InvalidArtifactRTException: For artifact
> {org.springframework.ldap:spring-ldap-core:null:pom}: The version cannot be
> empty.
> {quote}
> The POM looks like this:
> {quote}
>
> xmlns="http://maven.apache.org/POM/4.0.0";
> xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance";
> xsi:schemaLocation="http://maven.apache.org/POM/4.0.0
> http://maven.apache.org/maven-v4_0_0.xsd";>
>
> org.springframework.ldap
> spring-ldap-parent
> 1.3.0.RELEASE
>
> 4.0.0
> spring-ldap-core
> jar
> Spring LDAP Core
>
> ...
> {quote}
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://jira.codehaus.org/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Commented: (MINSTALL-70) install-file should take the version from the parent if the version for the artifact is missing in the POM
[
http://jira.codehaus.org/browse/MINSTALL-70?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=191170#action_191170
]
Eric Lewis commented on MINSTALL-70:
Here's the output from {{mvn:help effective-pom}}
$ mvn help:effective-pom
[INFO] Scanning for projects...
[INFO] Searching repository for plugin with prefix: 'help'.
[INFO] artifact org.apache.maven.plugins:maven-help-plugin: checking for
updates from Codehaus
[INFO]
[INFO] Building Spring LDAP Core
[INFO]task-segment: [help:effective-pom] (aggregator-style)
[INFO]
[INFO] [help:effective-pom {execution: default-cli}]
[INFO]
Effective POMs, after inheritance, interpolation, and profiles are applied:
http://maven.apache.org/POM/4.0.0";
xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance";
xsi:schemaLocation="http://maven.apache.org/POM/4.0.0
http://maven.apache.org/xsd/maven-4.0.0.xsd";>
4.0.0
spring-ldap-parent
org.springframework.ldap
1.3.0.RELEASE
org.springframework.ldap
spring-ldap-core
1.3.0.RELEASE
Spring LDAP Core
...
> install-file should take the version from the parent if the version for the
> artifact is missing in the POM
> --
>
> Key: MINSTALL-70
> URL: http://jira.codehaus.org/browse/MINSTALL-70
> Project: Maven 2.x Install Plugin
> Issue Type: Bug
> Components: install:install-file
>Affects Versions: 2.3
>Reporter: Eric Lewis
>
> Spring Source seems to release POM which have no version. According to the
> Maven philosophy this means that they inherit their parent's version.
> However, if I try
> {{mvn install:install-file -Dfile=spring-ldap-core-1.3.0.RELEASE.jar
> -DpomFile=pom.xml}}
> I get
> {quote}
> [INFO] Scanning for projects...
> [INFO] Searching repository for plugin with prefix: 'install'.
> [INFO]
>
> [INFO] Building Spring LDAP Core
> [INFO]task-segment: [install:install-file] (aggregator-style)
> [INFO]
>
> [INFO] [install:install-file {execution: default-cli}]
> [INFO]
>
> [ERROR] FATAL ERROR
> [INFO]
>
> [INFO] An invalid artifact was detected.
> This artifact might be in your project's POM, or it might have been included
> transitively during the resolution process. Here is the information we do
> have for this artifact:
> o GroupID: org.springframework.ldap
> o ArtifactID: spring-ldap-core
> o Version: <<< MISSING >>>
> o Type:pom
> [INFO]
>
> [INFO] Trace
> org.apache.maven.artifact.InvalidArtifactRTException: For artifact
> {org.springframework.ldap:spring-ldap-core:null:pom}: The version cannot be
> empty.
> {quote}
> The POM looks like this:
> {quote}
>
> xmlns="http://maven.apache.org/POM/4.0.0";
> xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance";
> xsi:schemaLocation="http://maven.apache.org/POM/4.0.0
> http://maven.apache.org/maven-v4_0_0.xsd";>
>
> org.springframework.ldap
> spring-ldap-parent
> 1.3.0.RELEASE
>
> 4.0.0
> spring-ldap-core
> jar
> Spring LDAP Core
>
> ...
> {quote}
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://jira.codehaus.org/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Commented: (MINSTALL-70) install-file should take the version from the parent if the version for the artifact is missing in the POM
[
http://jira.codehaus.org/browse/MINSTALL-70?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=191168#action_191168
]
Benjamin Bentmann commented on MINSTALL-70:
---
This looks like a duplicate of MINSTALL-55 so can you provide the debug logs of
the above command to verify that you were actually using plugin version 2.3 and
not something older?
> install-file should take the version from the parent if the version for the
> artifact is missing in the POM
> --
>
> Key: MINSTALL-70
> URL: http://jira.codehaus.org/browse/MINSTALL-70
> Project: Maven 2.x Install Plugin
> Issue Type: Bug
> Components: install:install-file
>Affects Versions: 2.3
>Reporter: Eric Lewis
>
> Spring Source seems to release POM which have no version. According to the
> Maven philosophy this means that they inherit their parent's version.
> However, if I try
> {{mvn install:install-file -Dfile=spring-ldap-core-1.3.0.RELEASE.jar
> -DpomFile=pom.xml}}
> I get
> {quote}
> [INFO] Scanning for projects...
> [INFO] Searching repository for plugin with prefix: 'install'.
> [INFO]
>
> [INFO] Building Spring LDAP Core
> [INFO]task-segment: [install:install-file] (aggregator-style)
> [INFO]
>
> [INFO] [install:install-file {execution: default-cli}]
> [INFO]
>
> [ERROR] FATAL ERROR
> [INFO]
>
> [INFO] An invalid artifact was detected.
> This artifact might be in your project's POM, or it might have been included
> transitively during the resolution process. Here is the information we do
> have for this artifact:
> o GroupID: org.springframework.ldap
> o ArtifactID: spring-ldap-core
> o Version: <<< MISSING >>>
> o Type:pom
> [INFO]
>
> [INFO] Trace
> org.apache.maven.artifact.InvalidArtifactRTException: For artifact
> {org.springframework.ldap:spring-ldap-core:null:pom}: The version cannot be
> empty.
> {quote}
> The POM looks like this:
> {quote}
>
> xmlns="http://maven.apache.org/POM/4.0.0";
> xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance";
> xsi:schemaLocation="http://maven.apache.org/POM/4.0.0
> http://maven.apache.org/maven-v4_0_0.xsd";>
>
> org.springframework.ldap
> spring-ldap-parent
> 1.3.0.RELEASE
>
> 4.0.0
> spring-ldap-core
> jar
> Spring LDAP Core
>
> ...
> {quote}
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://jira.codehaus.org/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Created: (MINSTALL-70) install-file should take the version from the parent if the version for the artifact is missing in the POM
install-file should take the version from the parent if the version for the
artifact is missing in the POM
--
Key: MINSTALL-70
URL: http://jira.codehaus.org/browse/MINSTALL-70
Project: Maven 2.x Install Plugin
Issue Type: Bug
Components: install:install-file
Affects Versions: 2.3
Reporter: Eric Lewis
Spring Source seems to release POM which have no version. According to the
Maven philosophy this means that they inherit their parent's version.
However, if I try
{{mvn install:install-file -Dfile=spring-ldap-core-1.3.0.RELEASE.jar
-DpomFile=pom.xml}}
I get
{quote}
[INFO] Scanning for projects...
[INFO] Searching repository for plugin with prefix: 'install'.
[INFO]
[INFO] Building Spring LDAP Core
[INFO]task-segment: [install:install-file] (aggregator-style)
[INFO]
[INFO] [install:install-file {execution: default-cli}]
[INFO]
[ERROR] FATAL ERROR
[INFO]
[INFO] An invalid artifact was detected.
This artifact might be in your project's POM, or it might have been included
transitively during the resolution process. Here is the information we do have
for this artifact:
o GroupID: org.springframework.ldap
o ArtifactID: spring-ldap-core
o Version: <<< MISSING >>>
o Type:pom
[INFO]
[INFO] Trace
org.apache.maven.artifact.InvalidArtifactRTException: For artifact
{org.springframework.ldap:spring-ldap-core:null:pom}: The version cannot be
empty.
{quote}
The POM looks like this:
{quote}
http://maven.apache.org/POM/4.0.0";
xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance";
xsi:schemaLocation="http://maven.apache.org/POM/4.0.0
http://maven.apache.org/maven-v4_0_0.xsd";>
org.springframework.ldap
spring-ldap-parent
1.3.0.RELEASE
4.0.0
spring-ldap-core
jar
Spring LDAP Core
...
{quote}
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://jira.codehaus.org/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Created: (MRELEASE-483) PrepareReleaseMojo always increments development version
PrepareReleaseMojo always increments development version Key: MRELEASE-483 URL: http://jira.codehaus.org/browse/MRELEASE-483 Project: Maven 2.x Release Plugin Issue Type: Bug Components: prepare Affects Versions: 2.0-beta-9 Environment: Mac Reporter: Noah Vihinen PrepareReleaseMojo always increments development version For example, if the latest development version is 1.3-SNAPSHOT. mvn --batch-mode -Dtag=yflex_library-1.0.1237 -DreleaseVersion=1.0.1237 -DdevelopmentVersion=1.0-SNAPSHOT release:prepare mvn --batch-mode -Dtag=yflex_library-1.0.1237 -DreleaseVersion=1.0.1237 -Dproject.dev.yahoo.yinst.yflex_library:yflex_library=1.0-SNAPSHOT release:prepare results in this line in the generated release.properties project.dev.yahoo.yinst.yflex_library\:yflex_library=1.4-SNAPSHOT even though I specified the development version to be 1.0-SNAPSHOT. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Closed: (MNG-3281) Revisit backwards compat of extensions (IT 0114)
[ http://jira.codehaus.org/browse/MNG-3281?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Benjamin Bentmann closed MNG-3281. -- Assignee: Benjamin Bentmann (was: Jason van Zyl) Resolution: Fixed Fix Version/s: (was: 3.0-alpha-4) 3.0-alpha-3 Fixed in [r815761|http://svn.apache.org/viewvc?view=rev&revision=815761]. Just to mention it, we can't completely cut off plugins from the extensions because plugins can inspect the execution plan or create&resolve artifacts. Those tasks require access to lifecycle mappings and artifact handlers, both contributed by extensions. We now have the following parent-child chain of class realms on trunk: core realm -> project realm -> plugin realm. The project realm is only present if the project actually declares any extensions, otherwise the plugin realm is a direct child of the core realm. The project realm aggregates all JARs from its build extensions so there's the potential for conflicts between extensions. For the moment, this should work well enough, more sophisticated class loader setups likely require more metadata in the extension JARs, e.g. what should be exported/shared and what is private impl. > Revisit backwards compat of extensions (IT 0114) > > > Key: MNG-3281 > URL: http://jira.codehaus.org/browse/MNG-3281 > Project: Maven 2 > Issue Type: Bug >Affects Versions: 3.0-alpha-1 >Reporter: Brett Porter >Assignee: Benjamin Bentmann > Fix For: 3.0-alpha-3 > > > currently, it 0114 doesn't pass due to the removal of extension support > we need to either: > - restore some form of backwards compat by loading the extension into the > expected place > - provide a graceful failure instead -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Difficulty while downloading jars using maven
Hi All, I’m facing difficulty while downloading jars using maven. This is the kind of exception I’m getting: java.lang.NoSuchMethodError: com.trend.iwss.jscan.appscan.runtime.PolicyProps: method ()V not found at com.trend.iwss.jscan.appscan.runtime.Session.(Session.java:58) at com.trend.iwss.jscan.appscan.runtime.Session.(Session.java:33) at com.trend.iwss.jscan.appscan.runtime.PolicyRuntime.preFilter(PolicyRuntime.java:128) at com.trend.iwss.jscan.appscan.runtime.ThreadPolicyRuntime.preFilter(ThreadPolicyRuntime.java:56) Seems like the corporate firewall is adding its own classes to the jars and corrupting it. On searching across forums, I found this: http://forums.sun.com/thread.jspa?threadID=5123159&messageID=9432999 Has any of you faced this issue, If yes please guide me about the next steps. Regards, Eklovya -- View this message in context: http://www.nabble.com/Difficulty-while-downloading-jars-using-maven-tp25471648p25471648.html Sent from the Maven - Issues mailing list archive at Nabble.com.
[jira] Created: (MSITE-428) site skin configurable also via POM (not only via site descriptor)
site skin configurable also via POM (not only via site descriptor) -- Key: MSITE-428 URL: http://jira.codehaus.org/browse/MSITE-428 Project: Maven 2.x Site Plugin Issue Type: New Feature Environment: environment independent Reporter: Christoph Pickl Priority: Minor as far as i can see the only possibility to define the skin of your site is via the site.xml descriptor. it would be nice if one could configure the skin within the pom.xml (below reporting/plugins/site-plugin/configuration). this would mean that specifying the skin in one of your super POMs would also immediately affect all your sub POMs. if someone could tell me where to change what, i would like to offer my help as a developer and write the necessary code myself... ~christoph -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Commented: (MDEP-230) Performance is really bad for large artifacts
[ http://jira.codehaus.org/browse/MDEP-230?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=191138#action_191138 ] Mark Bowman commented on MDEP-230: -- I am having similar problems. I have a tar.gz file which is 0.7Mb. It takes 3.5 minutes to unpack. The expansion to a temporary tar file is fast but the subsequent tar expansion is very slow. In fact the expansion seems to happen very quickly but the plugin than sits doing nothing (according to mvn -X) for several minutes. It doesn't even complain if you remove the tar file it reports to be expanding. > Performance is really bad for large artifacts > - > > Key: MDEP-230 > URL: http://jira.codehaus.org/browse/MDEP-230 > Project: Maven 2.x Dependency Plugin > Issue Type: Improvement > Components: unpack >Affects Versions: 2.1 > Environment: linux >Reporter: Jason Chaffee >Assignee: Brian Fox > > I have a 300mb tar.gz file that I need to unpack for one of my builds. I > takes over 10 minutes to unpack with the unpack goal. If I do it on the > cmd-line it takes less than 1 minute. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
