[jira] Commented: (MJAVADOC-97) enable internal/external dependency references as links
[ http://jira.codehaus.org/browse/MJAVADOC-97?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_90113 ] Richard van Nieuwenhoven commented on MJAVADOC-97: -- i know it is not the best solution but i needed a solution fast, any volunteers on beatifying this "nessesary" feature. maybe somewone can comine the effort with the xref generation, to solve the same problem for both projects > enable internal/external dependency references as links > > > Key: MJAVADOC-97 > URL: http://jira.codehaus.org/browse/MJAVADOC-97 > Project: Maven 2.x Javadoc Plugin > Issue Type: New Feature >Affects Versions: 2.1 >Reporter: Richard van Nieuwenhoven >Priority: Minor > Attachments: maven-javadoc-plugin-2.1.patch > > > This patch enables the java doc plugin to autmaticaly connect the dependent > javadoc pages as links. > There is no more need to add links in your pom's for internal and external > maven projects. > The plugin resolves the dependencies and adds the defined project url's > extended with "/apidocs" to the links in the plugin. > TODO: a warning occures when the project has no javadocs (or no maven > generated javadoc on its homepage) .. -- 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: (MECLIPSE-213) more jee support for wtp
[ http://jira.codehaus.org/browse/MECLIPSE-213?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_90114 ] Richard van Nieuwenhoven commented on MECLIPSE-213: --- Currently i use the mavenarchiver to generate a manifest. The problem is that wtp needs a manifest (with classpath) for multiy module projects. (And we do not want it to intrefere with the one generated by the jar plugin). The mavenarchiver can only be used if the jar names include the version, that is not the normal behavior of the maven-eclipse-plugin, i now made a extra option to change the project name to the "maven compatible" name with version. i can post this patch but it is based on the realeased 2.3 version. At the moment i do not have the time to diliver a patch based on the current SNAPSHOT. when you want it please report it here, because than i will make some checks first. > more jee support for wtp > > > Key: MECLIPSE-213 > URL: http://jira.codehaus.org/browse/MECLIPSE-213 > Project: Maven 2.x Eclipse Plugin > Issue Type: Improvement > Components: WTP support >Affects Versions: 2.3 > Environment: linux suse 10.0 eclipse 3.2.1 and wtp 1.5.1 java 1.5.0_8 >Reporter: Richard van Nieuwenhoven > Attachments: maven-eclipse-plugin-R494407.patch > > > I tried the new release 2.3 of the eclipse plugin and noteted that not alle > of my paches where included. > I re-pached the 2.3 version again this time i made my changes configurable so > they can be turned on and off. > my changes: > - prohibit dupicate entries in the classpath > provided system paths in combination with log4j/commons-logging/xerces > can easely create such problems > - system paths are only included in ears and war when they are inside the > project >bether behavior would be to exclude all system paths because the war and > ear plugin also ignore these > - an application.xml specialy for eclipse-wtp >this makes wtp ears function correctly it includes the eclipse project > modules instead of the maven generated jars > - manifest generation for wtp >wtp needs manifest files, but not the ones maven creates because they have > version names for all modules etc >this generates a wtp manifest that will be in a ons eclipse source > directory that is ignored my maven itself > use the parameters -Declipse.wtpmanifest=true > -Declipse.wtpapplicationxml=true to acivate the patch. > The manifest generator could be combined with the RadManifestWriter in the > future, they are almost the same. > regards, > Ritchie -- 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: (MECLIPSE-163) eclipe:eclipse 2.3-SNAPSHOT with wtp-1.5 fixes
[ http://jira.codehaus.org/browse/MECLIPSE-163?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_90115 ] Richard van Nieuwenhoven commented on MECLIPSE-163: --- not realy, but i have made a new one based on the released eclipse 2.3 version see MECLIPSE-213 > eclipe:eclipse 2.3-SNAPSHOT with wtp-1.5 fixes > -- > > Key: MECLIPSE-163 > URL: http://jira.codehaus.org/browse/MECLIPSE-163 > Project: Maven 2.x Eclipse Plugin > Issue Type: Improvement > Components: multiproject, WTP support >Affects Versions: 2.3 >Reporter: Richard van Nieuwenhoven > Fix For: 2.4 > > Attachments: maven-eclipse-plugin-R448503.patch > > > we needed eclipse:eclipse to function with wtp 1.5 but we had some problems > with the 2.3 SNAPSHOT version. > 1) create a seperate eardefinition for eclipse > this makes it possible to include the reactor modules as projects (not > as versioned packages) > 2) enable ejb3 projects ejb3 > 3) module types in the components file corrected (war ejb modules included > now with module-reference) > 4) created a manifest-writer to write a eclipse/wtp compatible manifest for > module dependencies > this sould probably be done in a generated resources directory, but for > now i put it in src/main/resources > i will include the patch file as an attachment. Any one interested can > include the sources in the SNAPSHOT. > i use the patch for jboss and it works good, ejb(3) and web deployment is now > functional from scratch. -- 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: (MCHECKSTYLE-72) NPE when run with Maven 2.1-SNAPSHOT
NPE when run with Maven 2.1-SNAPSHOT
Key: MCHECKSTYLE-72
URL: http://jira.codehaus.org/browse/MCHECKSTYLE-72
Project: Maven 2.x Checkstyle Plugin
Issue Type: Bug
Affects Versions: 2.2
Environment: Maven 2.1 built from trunk on 15 March 2007, 10:00AM
Checkstyle plugin built from trunk on 15 March 2007, 11:20
Reporter: Vincent Massol
I get:
{code}
[INFO] An error has occurred in Checkstyle report generation.
[INFO]
[INFO] Trace
org.apache.maven.lifecycle.LifecycleExecutionException: An error has occurred
in Checkstyle report generation.
at
org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoals(DefaultLifecycleExecutor.java:524)
at
org.apache.maven.lifecycle.DefaultLifecycleExecutor.forkProjectLifecycle(DefaultLifecycleExecutor.java:862)
at
org.apache.maven.lifecycle.DefaultLifecycleExecutor.forkLifecycle(DefaultLifecycleExecutor.java:699)
at
org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoals(DefaultLifecycleExecutor.java:470)
at
org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoalWithLifecycle(DefaultLifecycleExecutor.java:440)
at
org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoal(DefaultLifecycleExecutor.java:419)
at
org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoalAndHandleFailures(DefaultLifecycleExecutor.java:271)
at
org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeTaskSegments(DefaultLifecycleExecutor.java:238)
at
org.apache.maven.lifecycle.DefaultLifecycleExecutor.execute(DefaultLifecycleExecutor.java:146)
at org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:303)
at org.apache.maven.DefaultMaven.execute(DefaultMaven.java:123)
at
org.apache.maven.embedder.MavenEmbedder.execute(MavenEmbedder.java:907)
at org.apache.maven.cli.MavenCli.main(MavenCli.java:369)
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:585)
at
org.codehaus.plexus.classworlds.launcher.Launcher.launchEnhanced(Launcher.java:289)
at
org.codehaus.plexus.classworlds.launcher.Launcher.launch(Launcher.java:229)
at
org.codehaus.plexus.classworlds.launcher.Launcher.mainWithExitCode(Launcher.java:408)
at
org.codehaus.plexus.classworlds.launcher.Launcher.main(Launcher.java:351)
Caused by: org.apache.maven.plugin.MojoExecutionException: An error has
occurred in Checkstyle report generation.
at
org.apache.maven.reporting.AbstractMavenReport.execute(AbstractMavenReport.java:79)
at
org.apache.maven.plugin.DefaultPluginManager.executeMojo(DefaultPluginManager.java:598)
at
org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoals(DefaultLifecycleExecutor.java:499)
... 20 more
Caused by: java.lang.NullPointerException
at java.io.Reader.(Reader.java:61)
at java.io.InputStreamReader.(InputStreamReader.java:55)
at org.codehaus.plexus.util.IOUtil.copy(IOUtil.java:248)
at org.codehaus.plexus.util.IOUtil.toString(IOUtil.java:307)
at org.codehaus.plexus.util.IOUtil.toString(IOUtil.java:295)
at
org.apache.maven.reporting.AbstractMavenReport.getSiteDescriptor(AbstractMavenReport.java:134)
at
org.apache.maven.reporting.AbstractMavenReport.execute(AbstractMavenReport.java:70)
... 22 more
{code}
The POM I used:
{code}
org.apache.maven.plugins
maven-checkstyle-plugin
com.xpn.xwiki
xwiki-build-verifications
1.0-SNAPSHOT
**/Api.java,
**/xmlrpc/Attachment.java,
**/xmlrpc/SpaceSummary.java,
**/ViewAction.java,
**/ZipExplorer*.java,
**/content/**/*.java,
**/XWikiMessageTool.java
{code}
Thanks
-Vincent
--
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: (MJAVADOC-116) Impossible to aggregate javadoc if snapshot never built
Impossible to aggregate javadoc if snapshot never built
---
Key: MJAVADOC-116
URL: http://jira.codehaus.org/browse/MJAVADOC-116
Project: Maven 2.x Javadoc Plugin
Issue Type: Bug
Affects Versions: 2.2
Reporter: Damien Lecan
In a multi-module projet, I build an aggregated Javadoc for the site.
The project is built with "mvn clean deploy site-deploy"
When I add a new project, the next build always fails because the javadoc
plugin can't find at least one snapshot for the new added module
In the following example, I added a new module tele.persistance:pers-commons,
which have never been built before.
Maven tries to download it but it can't find it (never build before).
{noformat} [INFO] [site:site]
[WARNING] Unable to load parent project from repository: Could not find the
model file '/continuum-folders/working-directory/116/../pom.xml'.
[INFO] Skipped "About" report, file "index.html" already exists for the English
version.
[ERROR] VM #displayTree: error : too few arguments to macro. Wanted 2 got 0
[ERROR] VM #menuItem: error : too few arguments to macro. Wanted 1 got 0
[INFO] Generate "JavaDocs" report.
[INFO] snapshot tele:commons:1.2.0-alpha-1-SNAPSHOT: checking for updates from
mirror.snapshots
[INFO] snapshot tele.persistance:pers-data:1.2.0-alpha-1-SNAPSHOT: checking for
updates from mirror.snapshots
[INFO] snapshot tele.persistance:pers-api:1.2.0-alpha-1-SNAPSHOT: checking for
updates from mirror.snapshots
[INFO] snapshot tele.persistance:pers-commons:1.2.0-alpha-1-SNAPSHOT: checking
for updates from mirror.snapshots
Downloading:
http://proxy/maven2-snapshots/repository/tele/persistance/pers-commons/1.2.0-alpha-1-SNAPSHOT/pers-commons-1.2.0-alpha-1-SNAPSHOT.jar
[WARNING] Unable to get resource
'tele.persistance:pers-commons:jar:1.2.0-alpha-1-SNAPSHOT' from repository
mirror.snapshots (http://proxy/maven2-snapshots/repository)
[INFO]
[ERROR] BUILD ERROR
[INFO]
[INFO] Failed to resolve artifact.
Missing:
--
1) tele.persistance:pers-commons:jar:1.2.0-alpha-1-SNAPSHOT
Try downloading the file manually from the project website.
Then, install it using the command:
mvn install:install-file -DgroupId=tele.persistance
-DartifactId=pers-commons \
-Dversion=1.2.0-alpha-1-SNAPSHOT -Dpackaging=jar -Dfile=/path/to/file
Path to dependency:
1) tele.persistance:pers-dao:jar:1.2.0-alpha-1-SNAPSHOT
2) tele.persistance:pers-commons:jar:1.2.0-alpha-1-SNAPSHOT
--
1 required artifact is missing.
for artifact:
tele.persistance:pers-dao:jar:1.2.0-alpha-1-SNAPSHOT
from the specified remote repositories:
central (http://repo1.maven.org/maven2),
mirror.snapshots (http://proxy/maven2-snapshots/repository)
{noformat}
If I make an intermediate "install", everything works fine
--
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: (SCM-284) Add a pure java cvs provider
[ http://jira.codehaus.org/browse/SCM-284?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Emmanuel Venisse closed SCM-284. Resolution: Fixed Done. > Add a pure java cvs provider > > > Key: SCM-284 > URL: http://jira.codehaus.org/browse/SCM-284 > Project: Maven SCM > Issue Type: Improvement > Components: maven-scm-provider-cvs >Reporter: Emmanuel Venisse > Assigned To: Emmanuel Venisse > Fix For: 1.0 > > > This provider is required because lot of issues appear with native cvs > provider. Lot of official cvs clients doesn't understand some standard > parameters -- 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: (MAVENUPLOAD-1410) please could somebody correct castor-1.0, or give a hint how to use it?
[ http://jira.codehaus.org/browse/MAVENUPLOAD-1410?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_90123 ] THURNER rupert commented on MAVENUPLOAD-1410: - created CASTOR-1908. > please could somebody correct castor-1.0, or give a hint how to use it? > --- > > Key: MAVENUPLOAD-1410 > URL: http://jira.codehaus.org/browse/MAVENUPLOAD-1410 > Project: maven-upload-requests > Issue Type: Task >Reporter: THURNER rupert > Assigned To: Carlos Sanchez > > http://repo1.maven.org/maven2/castor/castor/1.0/ does not have a pom file. is > there a special maven version which can read such artefacts or the upload > somehow was wrong? -- 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: (MSITE-216) Don't break lines in apt generated table cells
Don't break lines in apt generated table cells -- Key: MSITE-216 URL: http://jira.codehaus.org/browse/MSITE-216 Project: Maven 2.x Site Plugin Issue Type: Improvement Environment: mvn 2.0.5 Reporter: Jerome Lacoste Priority: Trivial Attachments: APT-tables.png See attached screenshot. Is there a way to make this table look nicer ? I.e. get rid off the ? how does one create multiline table cells in APT format ? the parser introduces elements and that makes the rendering ugly I have a screenshot of the problem available kenney: http://www.flickr.com/photos/[EMAIL PROTECTED]/421928169/ can you paste the apt for the table? *--+--+ |command line | Java Mojo | *--+--+ | the VM exits as soon as the only | By default daemon threads are joined | | remaining threads are daemon threads | and interrupted once all known non | | | daemon threads have quitted. The join | | | timeout is customisable | | | The user might wish to further cleanup | | | cleanup by stopping the unresponsive | | | threads. | | | The user can disable the full extra | | | thread management (interrupt/join/[stop])| *--+--+ lacostej_: i'd say that the APT engine produced a one-on-one image of the source, quite nice ;) :) i guess you have to put everything on 1 line to make it render properly too bad you can't specify 'align=justify' what about \ ? ow crap: Line breaks must not be used inside titles and tables (which are line oriented blocks with implicit line breaks). and \ is a line break, instead of a continuation as is used everywhere else EODiscussion -- 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: (MSITE-216) Don't break lines in apt generated table cells
[ http://jira.codehaus.org/browse/MSITE-216?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_90124 ] Jerome Lacoste commented on MSITE-216: -- Jira screewed up my ATP table.. See http://pastebin.ca/395850 for a paste. > Don't break lines in apt generated table cells > -- > > Key: MSITE-216 > URL: http://jira.codehaus.org/browse/MSITE-216 > Project: Maven 2.x Site Plugin > Issue Type: Improvement > Environment: mvn 2.0.5 >Reporter: Jerome Lacoste >Priority: Trivial > Attachments: APT-tables.png > > > See attached screenshot. Is there a way to make this table look nicer ? I.e. > get rid off the ? >how does one create multiline table cells in APT format > ? the parser introduces elements and that makes the rendering ugly >I have a screenshot of the problem available >kenney: http://www.flickr.com/photos/[EMAIL > PROTECTED]/421928169/ > can you paste the apt for the table? > *--+--+ > |command line | Java Mojo > | > *--+--+ > | the VM exits as soon as the only | By default daemon threads are > joined| > | remaining threads are daemon threads | and interrupted once all known non > | > | | daemon threads have quitted. The > join| > | | timeout is customisable > | > | | The user might wish to further > cleanup | > | | cleanup by stopping the unresponsive > | > | | threads. > | > | | The user can disable the full extra > | > | | thread management > (interrupt/join/[stop])| > *--+--+ > lacostej_: i'd say that the APT engine produced a > one-on-one image of the source, quite nice ;) >:) > i guess you have to put everything on 1 line to make it > render properly > too bad you can't specify 'align=justify' > what about \ ? > ow crap: Line breaks must not be used inside titles and > tables (which are line oriented blocks with implicit line breaks). > and \ is a line break, instead of a continuation as is > used everywhere else > EODiscussion -- 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-1421) Upload JODConverter 2.1.1
Upload JODConverter 2.1.1 - Key: MAVENUPLOAD-1421 URL: http://jira.codehaus.org/browse/MAVENUPLOAD-1421 Project: maven-upload-requests Issue Type: Task Reporter: Mirko Nasato JODConverter (Java OpenDocument Converter) converts documents between different office formats, leveraging OpenOffice.org. -- 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: (MAVENUPLOAD-1419) Upload FreeMarker 2.3.9
[ http://jira.codehaus.org/browse/MAVENUPLOAD-1419?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_90127 ] Mirko Nasato commented on MAVENUPLOAD-1419: --- "Official blessing" on the FreeMarker mailing list: http://sourceforge.net/mailarchive/message.php?msg_id=38408657 > Upload FreeMarker 2.3.9 > --- > > Key: MAVENUPLOAD-1419 > URL: http://jira.codehaus.org/browse/MAVENUPLOAD-1419 > Project: maven-upload-requests > Issue Type: Task >Reporter: Mirko Nasato > -- 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: (MAVENUPLOAD-1410) please could somebody correct castor-1.0, or give a hint how to use it?
[ http://jira.codehaus.org/browse/MAVENUPLOAD-1410?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_90128 ] Tomasz Pik commented on MAVENUPLOAD-1410: - maybe you may use versions newer then 1.0, it looks that they have correct poms: http://repo1.maven.org/maven2/org/codehaus/castor/castor/ (note change of groupId)? > please could somebody correct castor-1.0, or give a hint how to use it? > --- > > Key: MAVENUPLOAD-1410 > URL: http://jira.codehaus.org/browse/MAVENUPLOAD-1410 > Project: maven-upload-requests > Issue Type: Task >Reporter: THURNER rupert > Assigned To: Carlos Sanchez > > http://repo1.maven.org/maven2/castor/castor/1.0/ does not have a pom file. is > there a special maven version which can read such artefacts or the upload > somehow was wrong? -- 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: (MECLIPSE-241) Compiler settings from parent project aren't used in wtp facet
Compiler settings from parent project aren't used in wtp facet
--
Key: MECLIPSE-241
URL: http://jira.codehaus.org/browse/MECLIPSE-241
Project: Maven 2.x Eclipse Plugin
Issue Type: Bug
Components: WTP support
Affects Versions: 2.3
Environment: maven 2.0.4 / maven 2.0.5
Reporter: Arnaud Heritier
Priority: Minor
Attachments: project-28.zip
In a parent POM I have :
{code:xml}
org.apache.maven.plugins
maven-compiler-plugin
1.5
1.5
{code}
And I have a submodule (a war) configure to generate wtp 1.5 settings :
{code:xml}
org.apache.maven.plugins
maven-eclipse-plugin
1.5
{code}
After running eclipse:eclipse I have the following in my
org.eclipse.wst.common.project.facet.core.xml :
{code:xml}
{code}
And not
{code:xml}
{code}
--
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: (MNG-2877) unable to resolve attached artifacts from reactor that are not in repo. (patch applied in svn and IT tests added)
[
http://jira.codehaus.org/browse/MNG-2877?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_90130
]
Stephane Nicoll commented on MNG-2877:
--
very cool. I was about to investigate this issue!
> unable to resolve attached artifacts from reactor that are not in repo.
> (patch applied in svn and IT tests added)
> -
>
> Key: MNG-2877
> URL: http://jira.codehaus.org/browse/MNG-2877
> Project: Maven 2
> Issue Type: Bug
> Components: Artifacts
>Affects Versions: 2.0.2, 2.0.3, 2.0.4, 2.0.5
>Reporter: Brian Fox
> Assigned To: Jason van Zyl
> Fix For: 2.0.6
>
>
> The patch has been applied here:
> https://svn.apache.org/repos/asf/maven/components/branches/maven-project-mdep64
> and the IT tests are already added to core-it but commented out from the
> suite. To enable it, uncomment this line: //suite.addTestSuite(
> MavenIT0118AttachedArtifactsInReactor.class );
> ---
> This is from MDEP-64:
> We have a project with a few sub-projects. Only one of those subprojects uses
> the maven-dependency-plugin, copying the jar file artifact from one of the
> sibling sub-projects. The dependency plugin has worked fine in another
> multi-project m2 buld and release when the dependency copy was only
> referencing projects outside the multi-project's project tree.
> But in the present multi-project release, copying that sibling jar file with
> the dependency plugin causes the mvn release:prepare step to fail, because it
> can't find the released version in the release repository. It doesn't care
> about referencing sibling project dependencies from the regular pom
> dependencies, it only chokes for the dependency:copy.
> Here's a diagram for the issue with three pseudo-poms. I omitted groupId's,
> scm, distributionManagement, and other content from the poms that were not
> necessary to communicate the basic issue. I've worked around this by using
> the antrun plugin, which is unpleasant and untidy. This seems like it might
> be related to MDEP-44.
> superproject/
> A/ -> no dependencies
> B/ -> dependency:copy A
> //superproject/pom.xml (abbrieviated)
>
> superproject
> pom
> 1.0.0.1-SNAPSHOT
>
> A
> B
>
>
> // superproject/A/pom.xml (abbrievated)
>
>
> superproject
> 1.0.0.1-SNAPSHOT
>
> A
> 1.0.0.1-SNAPSHOT
>
> // superproject/B/pom.xml (abbreviated)
>
>
> superproject
> 1.0.0.1-SNAPSHOT
>
> B
> war
> 1.0.0.1-SNAPSHOT
>
> FooWar
>
>
> org.apache.maven.plugins
> maven-dependency-plugin
>
>
> copy
>
> copy
>
> package
>
>
>
> A
> ${pom.version}
> jar
>
>
> ${project.build.directory}/${pom.build.finalName}/jars
>
>
>
>
>
>
>
>
> A
> ${pom.version}
>
>
>
> The error message during mvn release:prepare is basically:
> [INFO] Building B
> [INFO] task-segment: [clean, integration-test]
> [INFO]
>
> [INFO] [clean:clean]
> [INFO] [dependency:copy {execution: copy}]
> [INFO] Configured Artifact: :A:null:1.0.0.1:jar
> Downloading: /1.0.0.1/A-1.0.0.1.jar
> [WARNING] Unable to get resource from repository sizzle ( details>)
> [INFO]
>
> [ERROR] BUILD ERROR
> [INFO]
>
> [INFO] Failed to resolve artifact.
> GroupId:
> ArtifactId: A
> Version: 1.0.0.1
> Reason: Unable to download the artifact from any repository
--
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: (SCM-285) Generate all plexus descriptors
Generate all plexus descriptors --- Key: SCM-285 URL: http://jira.codehaus.org/browse/SCM-285 Project: Maven SCM Issue Type: Task Components: maven-scm-provider-bazaar, maven-scm-provider-clearcase, maven-scm-provider-cvs, maven-scm-provider-local, maven-scm-provider-perforce, maven-scm-provider-starteam, maven-scm-provider-svn, maven-scm-provider-synergy, maven-scm-provider-vss Reporter: Emmanuel Venisse Fix For: 1.0 -- 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: (SCM-285) Generate all plexus descriptors
[ http://jira.codehaus.org/browse/SCM-285?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Emmanuel Venisse updated SCM-285: - Assignee: Emmanuel Venisse Fix Version/s: 1.0 > Generate all plexus descriptors > --- > > Key: SCM-285 > URL: http://jira.codehaus.org/browse/SCM-285 > Project: Maven SCM > Issue Type: Task > Components: maven-scm-provider-bazaar, maven-scm-provider-clearcase, > maven-scm-provider-cvs, maven-scm-provider-local, > maven-scm-provider-perforce, maven-scm-provider-starteam, > maven-scm-provider-svn, maven-scm-provider-synergy, maven-scm-provider-vss >Reporter: Emmanuel Venisse > Assigned To: Emmanuel Venisse > Fix For: 1.0 > > -- 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: (SCM-286) Allow two provider implementations in classpath
Allow two provider implementations in classpath --- Key: SCM-286 URL: http://jira.codehaus.org/browse/SCM-286 Project: Maven SCM Issue Type: Improvement Reporter: Emmanuel Venisse will be useful for native cvs provider and java cvs provider -- 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: (SCM-286) Allow two provider implementations in classpath
[ http://jira.codehaus.org/browse/SCM-286?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Emmanuel Venisse updated SCM-286: - Assignee: Emmanuel Venisse Fix Version/s: 1.0 Component/s: maven-scm-api > Allow two provider implementations in classpath > --- > > Key: SCM-286 > URL: http://jira.codehaus.org/browse/SCM-286 > Project: Maven SCM > Issue Type: Improvement > Components: maven-scm-api >Reporter: Emmanuel Venisse > Assigned To: Emmanuel Venisse > Fix For: 1.0 > > > will be useful for native cvs provider and java cvs provider -- 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: (MECLIPSE-172) Don't add Default ClasspathContainer if a alternate JRE or a "Execution Environment" is configured as ClasspathContainer.
[
http://jira.codehaus.org/browse/MECLIPSE-172?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_90136
]
Renaud Denis commented on MECLIPSE-172:
---
(Ugly) workaround: put the custom JRE container before the default one in the
POM.
It will take the precedence in the eclipse classpath.
{code}
org.eclipse.jdt.launching.JRE_CONTAINER/org.eclipse.jdt.internal.debug.ui.launcher.StandardVMType/${eclipse.jre}
org.eclipse.jdt.launching.JRE_CONTAINER
{code}
> Don't add Default ClasspathContainer if a alternate JRE or a "Execution
> Environment" is configured as ClasspathContainer.
> -
>
> Key: MECLIPSE-172
> URL: http://jira.codehaus.org/browse/MECLIPSE-172
> Project: Maven 2.x Eclipse Plugin
> Issue Type: Bug
>Affects Versions: 2.2, 2.3
> Environment: Maven 2.0.4, Eclipse 3.2.1, Windows XP
>Reporter: Markus Grieder
> Attachments: patch.txt
>
>
> If have a Eclipse Workspace with Projects where some use Java 1.5 (Default
> JRE) and some Java 1.3
> For 1.3-Projects i have configured the following ClasspathContainer:
>
> org.eclipse.jdt.launching.JRE_CONTAINER/org.eclipse.jdt.internal.debug.ui.launcher.StandardVMType/server_jre
>
> This generates in ".classpath":
>
> path="org.eclipse.jdt.launching.JRE_CONTAINER/org.eclipse.jdt.internal.debug.ui.launcher.StandardVMType/server_jre"/>
> Which is wrong, because the Default JRE is Java 1.5, but the Project should
> only see Java 1.3-Libraries and not both.
> -> The Default ClasspathContainer should only be added if no JRE_CONTAINER
> (alternate JRE or a Execution Environment (>=Eclipse 3.2)) was specified. The
> attached Patch replace the "contains"-match with a "starts-with"-match, which
> only adds the Default ClasspathContainer if no classpathContainer is
> configured which starts with the "JRE_CONTAINER"-Path.
--
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: (SCM-287) ClearCase / Support for checking out from a tag and auto-creation of config specs
ClearCase / Support for checking out from a tag and auto-creation of config specs - Key: SCM-287 URL: http://jira.codehaus.org/browse/SCM-287 Project: Maven SCM Issue Type: New Feature Components: maven-scm-provider-clearcase Affects Versions: 1.0 Reporter: Arne Degenring Attachments: patch-maven-scm-provider-clearcase.txt, patch-maven-scm-site.txt A major limitation of the ClearCase plugin so far has been the missing support for checking out from a tag. As a consequence, the Maven release plugin could not be used. I implemented checking out from a tag, by supporting the automatic creation of config specs. The ClearCase SCM provider so far forced the user to create a config spec file at an external location and provide a link to it within the SCM url, e.g.: scm:clearcase:my_module_view:\\myserver\clearcase\configspecs\my_module.txt This URL format is still supported as it gives the user a maximum flexibility regarding config specs. However, it is quite unconvenient for users to provide config spec files in an external location. And for checking out from a tag, the config spec needs to be rewritten anyway. So, as an alternative, the user now can provide a SCM url like the following: scm:clearcase:my_module_view:load /MY_VOB/my/project/directory Such an url contains one load rule instead of a config spec file location. It is used by the ClearCase plugin to generate the following config spec in case no version tag has been specified: element * CHECKEDOUT element * /main/LATEST load In case a tag has been specified, the following config spec is created: element * CHECKEDOUT element * element -directory * /main/LATEST load I expect these auto-generated config specs to be sufficient and appropriate in at least 80% of the cases. The new functionality improves the ClearCase SCM integration significantly in these cases (much easier to use and more powerful). So, please apply the attached patch for maven-scm-provider-clearcase, including a patch for the documentation site. As the current URL format is still fully supported, this patch should not affect existing builds. (Afterwards, the maven-release-manager used by the Release plugin, can easily be completed by a ClearCase-specific ScmTranslator implementation to make the Release plugin fully usable with ClearCase.) -- 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: (SCM-286) Allow two provider implementations in classpath
[ http://jira.codehaus.org/browse/SCM-286?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Emmanuel Venisse closed SCM-286. Resolution: Fixed > Allow two provider implementations in classpath > --- > > Key: SCM-286 > URL: http://jira.codehaus.org/browse/SCM-286 > Project: Maven SCM > Issue Type: Improvement > Components: maven-scm-api >Reporter: Emmanuel Venisse > Assigned To: Emmanuel Venisse > Fix For: 1.0 > > > will be useful for native cvs provider and java cvs provider -- 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: (SCM-287) ClearCase / Support for checking out from a tag and auto-creation of config specs
[ http://jira.codehaus.org/browse/SCM-287?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Emmanuel Venisse updated SCM-287: - Fix Version/s: 1.0 > ClearCase / Support for checking out from a tag and auto-creation of config > specs > - > > Key: SCM-287 > URL: http://jira.codehaus.org/browse/SCM-287 > Project: Maven SCM > Issue Type: New Feature > Components: maven-scm-provider-clearcase >Affects Versions: 1.0 >Reporter: Arne Degenring > Fix For: 1.0 > > Attachments: patch-maven-scm-provider-clearcase.txt, > patch-maven-scm-site.txt > > > A major limitation of the ClearCase plugin so far has been the missing > support for checking out from a tag. As a consequence, the Maven release > plugin could not be used. I implemented checking out from a tag, by > supporting the automatic creation of config specs. > The ClearCase SCM provider so far forced the user to create a config spec > file at an external location and provide a link to it within the SCM url, > e.g.: > scm:clearcase:my_module_view:\\myserver\clearcase\configspecs\my_module.txt > This URL format is still supported as it gives the user a maximum flexibility > regarding config specs. However, it is quite unconvenient for users to > provide config spec files in an external location. And for checking out from > a tag, the config spec needs to be rewritten anyway. So, as an alternative, > the user now can provide a SCM url like the following: > scm:clearcase:my_module_view:load /MY_VOB/my/project/directory > Such an url contains one load rule instead of a config spec file location. It > is used by the ClearCase plugin to generate the following config spec in case > no version tag has been specified: > > element * CHECKEDOUT > element * /main/LATEST > load > In case a tag has been specified, the following config spec is created: > element * CHECKEDOUT > element * > element -directory * /main/LATEST > load > I expect these auto-generated config specs to be sufficient and appropriate > in at least 80% of the cases. The new functionality improves the ClearCase > SCM integration significantly in these cases (much easier to use and more > powerful). So, please apply the attached patch for > maven-scm-provider-clearcase, including a patch for the documentation site. > As the current URL format is still fully supported, this patch should not > affect existing builds. > (Afterwards, the maven-release-manager used by the Release plugin, can easily > be completed by a ClearCase-specific ScmTranslator implementation to make the > Release plugin fully usable with ClearCase.) -- 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: (SCM-287) ClearCase / Support for checking out from a tag and auto-creation of config specs
[ http://jira.codehaus.org/browse/SCM-287?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Emmanuel Venisse closed SCM-287. Assignee: Emmanuel Venisse Resolution: Fixed Applied. Thanks > ClearCase / Support for checking out from a tag and auto-creation of config > specs > - > > Key: SCM-287 > URL: http://jira.codehaus.org/browse/SCM-287 > Project: Maven SCM > Issue Type: New Feature > Components: maven-scm-provider-clearcase >Affects Versions: 1.0 >Reporter: Arne Degenring > Assigned To: Emmanuel Venisse > Fix For: 1.0 > > Attachments: patch-maven-scm-provider-clearcase.txt, > patch-maven-scm-site.txt > > > A major limitation of the ClearCase plugin so far has been the missing > support for checking out from a tag. As a consequence, the Maven release > plugin could not be used. I implemented checking out from a tag, by > supporting the automatic creation of config specs. > The ClearCase SCM provider so far forced the user to create a config spec > file at an external location and provide a link to it within the SCM url, > e.g.: > scm:clearcase:my_module_view:\\myserver\clearcase\configspecs\my_module.txt > This URL format is still supported as it gives the user a maximum flexibility > regarding config specs. However, it is quite unconvenient for users to > provide config spec files in an external location. And for checking out from > a tag, the config spec needs to be rewritten anyway. So, as an alternative, > the user now can provide a SCM url like the following: > scm:clearcase:my_module_view:load /MY_VOB/my/project/directory > Such an url contains one load rule instead of a config spec file location. It > is used by the ClearCase plugin to generate the following config spec in case > no version tag has been specified: > > element * CHECKEDOUT > element * /main/LATEST > load > In case a tag has been specified, the following config spec is created: > element * CHECKEDOUT > element * > element -directory * /main/LATEST > load > I expect these auto-generated config specs to be sufficient and appropriate > in at least 80% of the cases. The new functionality improves the ClearCase > SCM integration significantly in these cases (much easier to use and more > powerful). So, please apply the attached patch for > maven-scm-provider-clearcase, including a patch for the documentation site. > As the current URL format is still fully supported, this patch should not > affect existing builds. > (Afterwards, the maven-release-manager used by the Release plugin, can easily > be completed by a ClearCase-specific ScmTranslator implementation to make the > Release plugin fully usable with ClearCase.) -- 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: (MRM-303) 404 Error when trying to access archiva after install
404 Error when trying to access archiva after install - Key: MRM-303 URL: http://jira.codehaus.org/browse/MRM-303 Project: Archiva Issue Type: Bug Environment: Linux Reporter: David Bilge Priority: Critical Attachments: stacktrace.txt I pulled down the latest version of archiva from the svn and built it with "mvn install". If I run it with the integrated Jetty (mvn jetty:run) I get the following page as soon as I point my browser to http://host:9091/: "HTTP ERROR: 404 Caught Exception while registering Interceptor class pssEnvironmentCheckInterceptor" (... - see attachment) A similar thing happens, if I try to run it via integrated Plexus (this does not show an exception in the browser but on the console). -- 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: (SCM-34) Add PVCS support
[ http://jira.codehaus.org/browse/SCM-34?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_90143 ] Emmanuel Venisse commented on SCM-34: - In your code, I see lot of code related to cvs provider, I think you started your provider from it, but need to be clean > Add PVCS support > > > Key: SCM-34 > URL: http://jira.codehaus.org/browse/SCM-34 > Project: Maven SCM > Issue Type: Improvement > Components: maven-scm-provider-pvcs > Environment: any >Reporter: Nauman > Fix For: 1.0 > > Attachments: maven-scm-provider-pvcs.zip, MNG-SCM-34-maven-scm.patch, > MNG-SCM-34-maven-scm.patch > > > Please add pvcs support this will increase the potential number of developers > who can use maven dramatically. > I searched through the User and Developers archives for the keyword pvcs and > did not find any reference to either 1. A request to add support or 2. A > discussion of why this support should not be added. -- 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: (MPMD-41) Upgrade to PMD 3.9
[ http://jira.codehaus.org/browse/MPMD-41?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Daniel Kulp closed MPMD-41. --- Assignee: Daniel Kulp (was: Dennis Lundberg) Resolution: Fixed > Upgrade to PMD 3.9 > -- > > Key: MPMD-41 > URL: http://jira.codehaus.org/browse/MPMD-41 > Project: Maven 2.x Pmd Plugin > Issue Type: Task >Affects Versions: 2.1 >Reporter: Anthony Whitford > Assigned To: Daniel Kulp > Fix For: 2.2 > > > PMD 3.8 was released October 4, 2006. The Maven plugin should be updated too. > http://sourceforge.net/project/shownotes.php?release_id=452776&group_id=56262 -- 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-1422) Jfreechart 1.0.4 bundle upload request
Jfreechart 1.0.4 bundle upload request -- Key: MAVENUPLOAD-1422 URL: http://jira.codehaus.org/browse/MAVENUPLOAD-1422 Project: maven-upload-requests Issue Type: Task Reporter: Filippo Carone http://repository.openmindonline.it/_bundle-upload/jcommon-1.0.8-bundle.jar http://repository.openmindonline.it/_bundle-upload/jfreechart-1.0.4-bundle.jar http://repository.openmindonline.it/_bundle-upload/jfreechart-experimental-1.0.4-bundle.jar http://repository.openmindonline.it/_bundle-upload/jfreechart-swt-1.0.4-bundle.jar These are the upload bundles for the last version of JFreeChart. Please upload. -- 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: (MECLIPSE-242) RAD goal: missing lib-modules in .websettings
RAD goal: missing lib-modules in .websettings - Key: MECLIPSE-242 URL: http://jira.codehaus.org/browse/MECLIPSE-242 Project: Maven 2.x Eclipse Plugin Issue Type: Bug Affects Versions: 2.3, 2.4 Environment: IBM Rational Application Developer 6.0.x Reporter: Klaus Brunner Attachments: RadWebSettingsWriter.java The eclipse:rad goal does not currently write the lib-modules element of the .websettings file. When developing with RAD and WAS, this results in dependent projects' code not being packaged and deployed as part of the WAR by the RAD build and deploy process. This applies to project dependencies only. Adapted version of RadWebSettingsWriter.java is attached. -- 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: (CONTINUUM-1120) Default SCM Clearcase
[ http://jira.codehaus.org/browse/CONTINUUM-1120?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_90158 ] Arne Degenring commented on CONTINUUM-1120: --- Ausiàs, I think this works as designed. The SCM URL does NOT specifiy the view store directory to be used. You should not point it to an existing view storage directory. Instead, the SCM URL only specifies the location of a config spec file, and it will be used to create a NEW view: http://maven.apache.org/scm/clearcase.html The ClearCase provider by default uses the -vws parameter to specify the viewstore location \\\viewstore. If you want to behave it differently, you can specify a clearcase-settings.xml file in the .scm subdir of your home directory. You can specify another viewstore location, or even to disable the use of the -vws parameter. I like the latter option because at least in my customer's environment, this leads to an appropriate default behaviour. PS: You might be interested in the following issue: http://jira.codehaus.org/browse/SCM-287 > Default SCM Clearcase > - > > Key: CONTINUUM-1120 > URL: http://jira.codehaus.org/browse/CONTINUUM-1120 > Project: Continuum > Issue Type: Bug >Reporter: Ausiàs Armesto > Fix For: 1.1-alpha-# > > -- 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: (SCM-285) Generate all plexus descriptors
[ http://jira.codehaus.org/browse/SCM-285?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Emmanuel Venisse closed SCM-285. Resolution: Fixed > Generate all plexus descriptors > --- > > Key: SCM-285 > URL: http://jira.codehaus.org/browse/SCM-285 > Project: Maven SCM > Issue Type: Task > Components: maven-scm-provider-bazaar, maven-scm-provider-clearcase, > maven-scm-provider-cvs, maven-scm-provider-local, > maven-scm-provider-perforce, maven-scm-provider-starteam, > maven-scm-provider-svn, maven-scm-provider-synergy, maven-scm-provider-vss >Reporter: Emmanuel Venisse > Assigned To: Emmanuel Venisse > Fix For: 1.0 > > -- 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: (MAVENUPLOAD-1422) Jfreechart 1.0.4 bundle upload request
[ http://jira.codehaus.org/browse/MAVENUPLOAD-1422?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Carlos Sanchez closed MAVENUPLOAD-1422. --- Assignee: Carlos Sanchez Resolution: Fixed > Jfreechart 1.0.4 bundle upload request > -- > > Key: MAVENUPLOAD-1422 > URL: http://jira.codehaus.org/browse/MAVENUPLOAD-1422 > Project: maven-upload-requests > Issue Type: Task >Reporter: Filippo Carone > Assigned To: Carlos Sanchez > > http://repository.openmindonline.it/_bundle-upload/jcommon-1.0.8-bundle.jar > http://repository.openmindonline.it/_bundle-upload/jfreechart-1.0.4-bundle.jar > http://repository.openmindonline.it/_bundle-upload/jfreechart-experimental-1.0.4-bundle.jar > http://repository.openmindonline.it/_bundle-upload/jfreechart-swt-1.0.4-bundle.jar > These are the upload bundles for the last version of JFreeChart. > Please upload. -- 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: (MAVENUPLOAD-1419) Upload FreeMarker 2.3.9
[ http://jira.codehaus.org/browse/MAVENUPLOAD-1419?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Carlos Sanchez closed MAVENUPLOAD-1419. --- Assignee: Carlos Sanchez Resolution: Fixed > Upload FreeMarker 2.3.9 > --- > > Key: MAVENUPLOAD-1419 > URL: http://jira.codehaus.org/browse/MAVENUPLOAD-1419 > Project: maven-upload-requests > Issue Type: Task >Reporter: Mirko Nasato > Assigned To: Carlos Sanchez > -- 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: (MAVENUPLOAD-1421) Upload JODConverter 2.1.1
[ http://jira.codehaus.org/browse/MAVENUPLOAD-1421?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Carlos Sanchez closed MAVENUPLOAD-1421. --- Assignee: Carlos Sanchez Resolution: Fixed > Upload JODConverter 2.1.1 > - > > Key: MAVENUPLOAD-1421 > URL: http://jira.codehaus.org/browse/MAVENUPLOAD-1421 > Project: maven-upload-requests > Issue Type: Task >Reporter: Mirko Nasato > Assigned To: Carlos Sanchez > > JODConverter (Java OpenDocument Converter) converts documents between > different office formats, leveraging OpenOffice.org. -- 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: (MAVENUPLOAD-1420) Upload Struts 2 Spring Web Flow Plugin 1.0.3
[ http://jira.codehaus.org/browse/MAVENUPLOAD-1420?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_90169 ] Carlos Sanchez commented on MAVENUPLOAD-1420: - where is the parent? > Upload Struts 2 Spring Web Flow Plugin 1.0.3 > > > Key: MAVENUPLOAD-1420 > URL: http://jira.codehaus.org/browse/MAVENUPLOAD-1420 > Project: maven-upload-requests > Issue Type: Wish >Reporter: Matt Raible > > http://www.nabble.com/Re%3A-Spring-Web-Flow-Plugin-in-Maven-Repo--p9486418.html -- 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: (MAVENUPLOAD-1415) rails-integration for jruby-extras
[ http://jira.codehaus.org/browse/MAVENUPLOAD-1415?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Carlos Sanchez closed MAVENUPLOAD-1415. --- Assignee: Carlos Sanchez Resolution: Fixed > rails-integration for jruby-extras > -- > > Key: MAVENUPLOAD-1415 > URL: http://jira.codehaus.org/browse/MAVENUPLOAD-1415 > Project: maven-upload-requests > Issue Type: Task >Reporter: Robert Egglestone > Assigned To: Carlos Sanchez > > Please place this release in the maven repository. > It's an add-on for JRuby, hosted as part of ruby-extras. > Release notes: > Java web applications are typically packaged as WAR files in preparation for > distribution and deployment to J2EE servers. Rails Integration allows the > packaging of Ruby on Rails applications in a similar form, to enable seamless > deployment to Java servers. > Documentation can be found at > http://www.headius.com/jrubywiki/index.php/Rails_Integration -- 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: (MAVENUPLOAD-1417) Add strutstestcase-2.1.3-1.2-2.4
[ http://jira.codehaus.org/browse/MAVENUPLOAD-1417?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Carlos Sanchez closed MAVENUPLOAD-1417. --- Assignee: Carlos Sanchez Resolution: Fixed > Add strutstestcase-2.1.3-1.2-2.4 > > > Key: MAVENUPLOAD-1417 > URL: http://jira.codehaus.org/browse/MAVENUPLOAD-1417 > Project: maven-upload-requests > Issue Type: Task >Reporter: Victor Letunovsky > Assigned To: Carlos Sanchez > Attachments: strutstestcase-2.1.3-1.2-2.4-bundle.jar, > strutstestcase-2.1.3-1.2-2.4-bundle.jar, > strutstestcase-2.1.3-1.2-2.4-bundle.jar > > > Bundle attached > http://strutstestcase.sourceforge.net/ > StrutsTestCase for JUnit is an extension of the standard JUnit TestCase class > that provides facilities for testing code based on the Struts framework. -- 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: (SUREFIRE-300) NPE in SurefirePlugin.constructSurefireBooter()
[ http://jira.codehaus.org/browse/SUREFIRE-300?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_90170 ] Brad Szabo commented on SUREFIRE-300: - This appears to happen if you do not have a dependency on junit declared in your project. > NPE in SurefirePlugin.constructSurefireBooter() > --- > > Key: SUREFIRE-300 > URL: http://jira.codehaus.org/browse/SUREFIRE-300 > Project: Maven Surefire > Issue Type: Bug >Affects Versions: 2.3 >Reporter: Niklas Gustavsson > Assigned To: Jason van Zyl > Fix For: 2.3.1 > > Attachments: npe.log > > > SurefirePlugin.constructSurefireBooter() throws NPE when no testcases are > present in the project. The log attached is from building FtpServer admin-gui > using the 2.3 version of maven-surefire-plugin: > http://svn.apache.org/repos/asf/incubator/ftpserver/trunk/admin-gui/ -- 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: (CONTINUUM-1213) Patch to easily run continuum jetty with postgres
Patch to easily run continuum jetty with postgres - Key: CONTINUUM-1213 URL: http://jira.codehaus.org/browse/CONTINUUM-1213 Project: Continuum Issue Type: Improvement Components: Database Affects Versions: 1.1-alpha-# Reporter: thierry lach Priority: Minor Attachments: postgres-jetty.patch The attached patch will allow running jetty against a postgres database. As configured, postgres must be localhost, and have two databases named continuum and users which are accessible by user continuum with password continuum. It uses a profile and a property to point to a different jetty-env.xml file with that configuration in it. It can be launched with the command mvn -Ppostgres81 jetty:run from within the continuum-webapp directory. I think (but haven't tested it) that the patch also allows pointing to any arbitrary jetty-env.xml file by using a launch similar to: mvn -Djetty.env.xml=/path/to/jetty-env.xml jetty:run -- 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: (MECLIPSE-241) Compiler settings from parent project aren't used in wtp facet
[
http://jira.codehaus.org/browse/MECLIPSE-241?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Arnaud Heritier closed MECLIPSE-241.
Resolution: Fixed
Fix Version/s: 2.4
Fixed. SNAPSHOT deployed.
> Compiler settings from parent project aren't used in wtp facet
> --
>
> Key: MECLIPSE-241
> URL: http://jira.codehaus.org/browse/MECLIPSE-241
> Project: Maven 2.x Eclipse Plugin
> Issue Type: Bug
> Components: WTP support
>Affects Versions: 2.3
> Environment: maven 2.0.4 / maven 2.0.5
>Reporter: Arnaud Heritier
> Assigned To: Arnaud Heritier
>Priority: Minor
> Fix For: 2.4
>
> Attachments: project-28.zip
>
>
> In a parent POM I have :
> {code:xml}
>
> org.apache.maven.plugins
> maven-compiler-plugin
>
> 1.5
> 1.5
>
>
> {code}
> And I have a submodule (a war) configure to generate wtp 1.5 settings :
> {code:xml}
>
> org.apache.maven.plugins
> maven-eclipse-plugin
>
> 1.5
>
>
> {code}
> After running eclipse:eclipse I have the following in my
> org.eclipse.wst.common.project.facet.core.xml :
> {code:xml}
>
>
>
>
>
>
> {code}
> And not
> {code:xml}
>
>
>
>
>
>
> {code}
--
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-204) two dependencies with the same groupId and artifactId can not be released
two dependencies with the same groupId and artifactId can not be released - Key: MRELEASE-204 URL: http://jira.codehaus.org/browse/MRELEASE-204 Project: Maven 2.x Release Plugin Issue Type: Improvement Affects Versions: 2.0-beta-5 Environment: linux, maven2, java1.5/1.4 Reporter: kristian meier Priority: Minor Attachments: patch.txt I have pom which has something like de.tipitaka utils 1.0-SNAPSHOT de.tipitaka utils 1.0-SNAPSHOT sources and the maven-release-manager only increases the version at the first of these dependencies. the attached patch against the trunk of maven-release-manager fixes the problem and works with my porject. -- 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: (MECLIPSE-108) .wtpmodules with version 2.4 for javax.servlet:servlet-api:2.3
[ http://jira.codehaus.org/browse/MECLIPSE-108?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Arnaud Heritier closed MECLIPSE-108. Resolution: Fixed Fix Version/s: 2.4 Fixed. SNAPSHOT deployed. > .wtpmodules with version 2.4 for javax.servlet:servlet-api:2.3 > -- > > Key: MECLIPSE-108 > URL: http://jira.codehaus.org/browse/MECLIPSE-108 > Project: Maven 2.x Eclipse Plugin > Issue Type: Bug > Components: WTP support >Affects Versions: 2.2 >Reporter: Daniel Schulz > Assigned To: Arnaud Heritier > Fix For: 2.4 > > Attachments: MECLIPSE-108-maven-eclipse-plugin.patch > > > specified the following dependency: > > > servlet-api > javax.servlet > 2.3 > > mvn eclipse:clean eclipse:eclipse produces the following .wtpmodules snippet: > > 2.4 > > > think, it should be 2.3. looks like it was the intention > of the plugin to detect the servlet-api version by processing the dependency > list. there is a method resolveServletVersion() in > org.apache.maven.plugin.eclipse.writers.AbstractWtpResourceWriter. -- 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: (MECLIPSE-198) EJB version is not resloved
[ http://jira.codehaus.org/browse/MECLIPSE-198?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Arnaud Heritier closed MECLIPSE-198. Resolution: Fixed Fix Version/s: 2.4 Fixed. SNAPSHOT deployed. > EJB version is not resloved > --- > > Key: MECLIPSE-198 > URL: http://jira.codehaus.org/browse/MECLIPSE-198 > Project: Maven 2.x Eclipse Plugin > Issue Type: Bug > Components: WTP support >Affects Versions: 2.2 > Environment: all >Reporter: David Rabinowitz > Assigned To: Arnaud Heritier > Fix For: 2.4 > > > When creating an project marked as ejb, and ejbVersion=3.0, the jst.ejb facet > remains as with version 2.1. This is since the relevant method, > resolveEjbVersion() is implemented to return a fixed constant "2.1". See > http://maven.apache.org/plugins/maven-eclipse-plugin/xref/org/apache/maven/plugin/eclipse/writers/AbstractWtpResourceWriter.html#237 > I guess the implmentation should look like the adjacent > resolveServletVersion() or resolveJ2eeVersion() methods -- 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: (MECLIPSE-220) Incorrect eclipse facet information when doing mvn eclipse:eclipse for war and ejb projects.
[ http://jira.codehaus.org/browse/MECLIPSE-220?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Arnaud Heritier closed MECLIPSE-220. Resolution: Fixed Fix Version/s: 2.4 Patch reviewed and applied. Thx. Issue Fixed. SNAPSHOT deployed. > Incorrect eclipse facet information when doing mvn eclipse:eclipse for war > and ejb projects. > > > Key: MECLIPSE-220 > URL: http://jira.codehaus.org/browse/MECLIPSE-220 > Project: Maven 2.x Eclipse Plugin > Issue Type: Bug > Components: WTP support >Affects Versions: 2.3 > Environment: maven 2.0.4 > maven-eclipse-plugin 2.3 >Reporter: Minto van der Sluis > Assigned To: Arnaud Heritier > Fix For: 2.4 > > Attachments: proper-facet.patch > > > When running 'mvn eclipse:eclipse' the results do not take the proper > servlet-api en ejb-api into account. > ejb version is not taken into account (see > http://jira.codehaus.org/browse/MECLIPSE-198) > servlet api version is not taken into account (see > http://jira.codehaus.org/browse/MECLIPSE-108) > I have fixed these problems locally, but looking at MECLIPSE-108 is wonder if > what I did is correct . Still my solution works for me. I wonder what the > difference is between config.getProject().getArtifacts() and > config.getProject().getDependencies() . Why in the existing implementation is > resolveServletVersion using getArtifacts() and resolveJ2eeVersion using > getDependencies() ? My solutions uses getDependencies() only and works for > me. > What I actually did is the following: > - I switched the 2 loops in getDependencyVersion. I think the order of > ids/names being looked up is more important than the order of the > dependencies. So first look for servlet-api then for servletapi then for > geronimo-spec-servlet. (something alike for ejb). > - When no servlet version was found use the J2EE version (resolveJ2eeVersion) > to determine the servlet version to be used. > - Implemented resolveEjbVersion along the lines of resolveServletVersion. > - Changed resolveJ2eeVersion to work along the line of resolveServletVersion. > - Fixed a glitch in resolveJavaVersion, where the getCompilerSourceVersion > was retrieved but not used. > Hope my efforts are usefull for others. ;-) > regards, > misl -- 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: (SUREFIRE-300) NPE in SurefirePlugin.constructSurefireBooter()
[ http://jira.codehaus.org/browse/SUREFIRE-300?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_90178 ] Brad Szabo commented on SUREFIRE-300: - I should clarify, this NPE occurs if you do not have a dependency on either 'junit' or 'testng' declared in your project. > NPE in SurefirePlugin.constructSurefireBooter() > --- > > Key: SUREFIRE-300 > URL: http://jira.codehaus.org/browse/SUREFIRE-300 > Project: Maven Surefire > Issue Type: Bug >Affects Versions: 2.3 >Reporter: Niklas Gustavsson > Assigned To: Jason van Zyl > Fix For: 2.3.1 > > Attachments: npe.log > > > SurefirePlugin.constructSurefireBooter() throws NPE when no testcases are > present in the project. The log attached is from building FtpServer admin-gui > using the 2.3 version of maven-surefire-plugin: > http://svn.apache.org/repos/asf/incubator/ftpserver/trunk/admin-gui/ -- 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: (MNG-2876) versionrange doesn't handle singluar version correctly (tests and patch already in svn)
[ http://jira.codehaus.org/browse/MNG-2876?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Brian Fox updated MNG-2876: --- Assignee: Brian Fox (was: Jason van Zyl) Fix Version/s: (was: 2.0.6) 2.0.x Discussed with Kenney via email: http://www.nabble.com/version-range-question-tf3250482s177.html and irc: http://dev.rectang.com/logs/codehaus/%23maven/20070315.html. The patch as written is currently not going to work. I will take this back and see. I think the most likely resolution is to work around inside my plugin, but I will probably add better comments to the javadoc in versionRange because it's confusing the way it is. Any fix has plenty of potential to break things. Ultimately this needs to be addressed in 2.1 > versionrange doesn't handle singluar version correctly (tests and patch > already in svn) > --- > > Key: MNG-2876 > URL: http://jira.codehaus.org/browse/MNG-2876 > Project: Maven 2 > Issue Type: Bug > Components: Artifacts >Affects Versions: 2.0.2, 2.0.3, 2.0.4, 2.0.5 >Reporter: Brian Fox > Assigned To: Brian Fox > Fix For: 2.0.x > > > I'm still having trouble with this. I wrote a sample class to show my > problem. The issue is that all the contains calls are correct except that a > singular version ie "2.0.5" always returns true. Is this an artifact bug, or > am I doing something wrong? According to the javadoc for the method (shown in > my original post below) the singular version is allowed as a version range. > The tests and fix are here: > https://svn.apache.org/repos/asf/maven/plugins/branches/maven-artifact-version-range-fix > > I just need someone to take a look and I can apply. -- 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: (CONTINUUM-991) Add meta refresh header to summary pages
[ http://jira.codehaus.org/browse/CONTINUUM-991?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] thierry lach updated CONTINUUM-991: --- Attachment: continuum-991.patch Patch here. Only difference is that I set the refresh at 300 (5 minutes) instead of 900 (15 minutes). > Add meta refresh header to summary pages > > > Key: CONTINUUM-991 > URL: http://jira.codehaus.org/browse/CONTINUUM-991 > Project: Continuum > Issue Type: New Feature > Components: Web - UI >Reporter: John Didion >Priority: Minor > Fix For: 1.1-alpha-2 > > Attachments: continuum-991.patch > > > It's nice to refresh summary pages automatically to update build statuses > without the user having to continually click the refresh button. > I didn't include a patch because I'm working against the Maestro codebase, > which has migrated all the UI to jsp. Should be the same concept, though. > Just add to the section. -- 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: (MRM-303) 404 Error when trying to access archiva after install
[ http://jira.codehaus.org/browse/MRM-303?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_90187 ] Rod Coffin commented on MRM-303: I am having the exact same issue after updating Archiva from trunk. I have tried this on several machines including two MacOS laptops and a CentOS server. > 404 Error when trying to access archiva after install > - > > Key: MRM-303 > URL: http://jira.codehaus.org/browse/MRM-303 > Project: Archiva > Issue Type: Bug > Environment: Linux >Reporter: David Bilge >Priority: Critical > Attachments: stacktrace.txt > > > I pulled down the latest version of archiva from the svn and built it with > "mvn install". If I run it with the integrated Jetty (mvn jetty:run) I get > the following page as soon as I point my browser to http://host:9091/: > "HTTP ERROR: 404 > Caught Exception while registering Interceptor class > pssEnvironmentCheckInterceptor" > (... - see attachment) > A similar thing happens, if I try to run it via integrated Plexus (this does > not show an exception in the browser but on the console). -- 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: (MRRESOURCES-14) Running the process goal fails if there is no target directory
[
http://jira.codehaus.org/browse/MRRESOURCES-14?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Daniel Kulp updated MRRESOURCES-14:
---
Fix Version/s: 1.0-alpha-4
> Running the process goal fails if there is no target directory
> --
>
> Key: MRRESOURCES-14
> URL: http://jira.codehaus.org/browse/MRRESOURCES-14
> Project: Maven 2.x Remote Resources Plugin
> Issue Type: Bug
>Affects Versions: 1.0-alpha-3
> Environment: Windows XP
>Reporter: Franz Allan Valencia See
> Assigned To: Daniel Kulp
>Priority: Critical
> Fix For: 1.0-alpha-4
>
>
> {panel}
> Embedded error: $\{basedir\}\target\.plxarc (The system cannot find the path
> specified)
> {panel}
--
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: (MRRESOURCES-15) ClassCast Exception happens when depending on the snapshot artifacts
[ http://jira.codehaus.org/browse/MRRESOURCES-15?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Daniel Kulp updated MRRESOURCES-15: --- Fix Version/s: 1.0-alpha-4 > ClassCast Exception happens when depending on the snapshot artifacts > > > Key: MRRESOURCES-15 > URL: http://jira.codehaus.org/browse/MRRESOURCES-15 > Project: Maven 2.x Remote Resources Plugin > Issue Type: Bug >Affects Versions: 1.0-alpha-3 >Reporter: Balaji Ravi > Assigned To: Daniel Kulp >Priority: Critical > Fix For: 1.0-alpha-4 > > > The remote resources plugin throws the following ClassCastException when > there are snapshot artifacts. > INFO] > [ERROR] FATAL ERROR > [INFO] > > [INFO] org.apache.maven.model.Repository > [INFO] > > [INFO] Trace > java.lang.ClassCastException: org.apache.maven.model.Repository > at > org.apache.maven.artifact.repository.metadata.DefaultRepositoryMetada > taManager.mergeMetadata(DefaultRepositoryMetadataManager.java:161) > at > org.apache.maven.artifact.repository.metadata.DefaultRepositoryMetada > taManager.resolve(DefaultRepositoryMetadataManager.java:134) > at > org.apache.maven.artifact.transform.AbstractVersionTransformation.res > olveVersion(AbstractVersionTransformation.java:65) > at > org.apache.maven.artifact.transform.SnapshotTransformation.transformF > orResolve(SnapshotTransformation.java:63) > at > org.apache.maven.artifact.transform.DefaultArtifactTransformationMana > ger.transformForResolve(DefaultArtifactTransformationManager.java:43) > at > org.apache.maven.artifact.resolver.DefaultArtifactResolver.resolve(De > faultArtifactResolver.java:114) > at > org.apache.maven.artifact.resolver.DefaultArtifactResolver.resolve(De > faultArtifactResolver.java:73) > at > org.apache.maven.project.DefaultMavenProjectBuilder.findModelFromRepo > sitory(DefaultMavenProjectBuilder.java:482) > at > org.apache.maven.project.DefaultMavenProjectBuilder.assembleLineage(D > efaultMavenProjectBuilder.java:1194) > at > org.apache.maven.project.DefaultMavenProjectBuilder.buildInternal(Def > aultMavenProjectBuilder.java:697) > at > org.apache.maven.project.DefaultMavenProjectBuilder.buildFromReposito > ry(DefaultMavenProjectBuilder.java:230) > at > org.apache.maven.plugin.resources.remote.ProcessRemoteResourcesMojo.g > etProjects(ProcessRemoteResourcesMojo.java:408) > at > org.apache.maven.plugin.resources.remote.ProcessRemoteResourcesMojo.e > xecute(ProcessRemoteResourcesMojo.java:273) > at > org.apache.maven.plugin.DefaultPluginManager.executeMojo(DefaultPlugi > nManager.java:420) > at > org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoals(Defa > ultLifecycleExecutor.java:539) > at > org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoalWithLi > fecycle(DefaultLifecycleExecutor.java:480) > at > org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoal(Defau > ltLifecycleExecutor.java:459) > at > org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoalAndHan > dleFailures(DefaultLifecycleExecutor.java:311) > at > org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeTaskSegmen > ts(DefaultLifecycleExecutor.java:278) > at > org.apache.maven.lifecycle.DefaultLifecycleExecutor.execute(DefaultLi > fecycleExecutor.java:143) > at org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:330) > at org.apache.maven.DefaultMaven.execute(DefaultMaven.java:123) > at org.apache.maven.cli.MavenCli.main(MavenCli.java:272) > at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) > at > sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl. > java:39) > at > sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAcces > sorImpl.java:25) > at java.lang.reflect.Method.invoke(Method.java:585) > 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) > -- 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: (MRRESOURCES-15) ClassCast Exception happens when depending on the snapshot artifacts
[ http://jira.codehaus.org/browse/MRRESOURCES-15?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Daniel Kulp closed MRRESOURCES-15. -- Resolution: Fixed > ClassCast Exception happens when depending on the snapshot artifacts > > > Key: MRRESOURCES-15 > URL: http://jira.codehaus.org/browse/MRRESOURCES-15 > Project: Maven 2.x Remote Resources Plugin > Issue Type: Bug >Affects Versions: 1.0-alpha-3 >Reporter: Balaji Ravi > Assigned To: Daniel Kulp >Priority: Critical > Fix For: 1.0-alpha-4 > > > The remote resources plugin throws the following ClassCastException when > there are snapshot artifacts. > INFO] > [ERROR] FATAL ERROR > [INFO] > > [INFO] org.apache.maven.model.Repository > [INFO] > > [INFO] Trace > java.lang.ClassCastException: org.apache.maven.model.Repository > at > org.apache.maven.artifact.repository.metadata.DefaultRepositoryMetada > taManager.mergeMetadata(DefaultRepositoryMetadataManager.java:161) > at > org.apache.maven.artifact.repository.metadata.DefaultRepositoryMetada > taManager.resolve(DefaultRepositoryMetadataManager.java:134) > at > org.apache.maven.artifact.transform.AbstractVersionTransformation.res > olveVersion(AbstractVersionTransformation.java:65) > at > org.apache.maven.artifact.transform.SnapshotTransformation.transformF > orResolve(SnapshotTransformation.java:63) > at > org.apache.maven.artifact.transform.DefaultArtifactTransformationMana > ger.transformForResolve(DefaultArtifactTransformationManager.java:43) > at > org.apache.maven.artifact.resolver.DefaultArtifactResolver.resolve(De > faultArtifactResolver.java:114) > at > org.apache.maven.artifact.resolver.DefaultArtifactResolver.resolve(De > faultArtifactResolver.java:73) > at > org.apache.maven.project.DefaultMavenProjectBuilder.findModelFromRepo > sitory(DefaultMavenProjectBuilder.java:482) > at > org.apache.maven.project.DefaultMavenProjectBuilder.assembleLineage(D > efaultMavenProjectBuilder.java:1194) > at > org.apache.maven.project.DefaultMavenProjectBuilder.buildInternal(Def > aultMavenProjectBuilder.java:697) > at > org.apache.maven.project.DefaultMavenProjectBuilder.buildFromReposito > ry(DefaultMavenProjectBuilder.java:230) > at > org.apache.maven.plugin.resources.remote.ProcessRemoteResourcesMojo.g > etProjects(ProcessRemoteResourcesMojo.java:408) > at > org.apache.maven.plugin.resources.remote.ProcessRemoteResourcesMojo.e > xecute(ProcessRemoteResourcesMojo.java:273) > at > org.apache.maven.plugin.DefaultPluginManager.executeMojo(DefaultPlugi > nManager.java:420) > at > org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoals(Defa > ultLifecycleExecutor.java:539) > at > org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoalWithLi > fecycle(DefaultLifecycleExecutor.java:480) > at > org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoal(Defau > ltLifecycleExecutor.java:459) > at > org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoalAndHan > dleFailures(DefaultLifecycleExecutor.java:311) > at > org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeTaskSegmen > ts(DefaultLifecycleExecutor.java:278) > at > org.apache.maven.lifecycle.DefaultLifecycleExecutor.execute(DefaultLi > fecycleExecutor.java:143) > at org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:330) > at org.apache.maven.DefaultMaven.execute(DefaultMaven.java:123) > at org.apache.maven.cli.MavenCli.main(MavenCli.java:272) > at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) > at > sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl. > java:39) > at > sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAcces > sorImpl.java:25) > at java.lang.reflect.Method.invoke(Method.java:585) > 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) > -- 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: (MRRESOURCES-14) Running the process goal fails if there is no target directory
[
http://jira.codehaus.org/browse/MRRESOURCES-14?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Daniel Kulp closed MRRESOURCES-14.
--
Resolution: Fixed
If no resources are unpacked/generated, don't create the .plxarc file as it
isn't needed.
> Running the process goal fails if there is no target directory
> --
>
> Key: MRRESOURCES-14
> URL: http://jira.codehaus.org/browse/MRRESOURCES-14
> Project: Maven 2.x Remote Resources Plugin
> Issue Type: Bug
>Affects Versions: 1.0-alpha-3
> Environment: Windows XP
>Reporter: Franz Allan Valencia See
> Assigned To: Daniel Kulp
>Priority: Critical
> Fix For: 1.0-alpha-4
>
>
> {panel}
> Embedded error: $\{basedir\}\target\.plxarc (The system cannot find the path
> specified)
> {panel}
--
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: (MNG-2831) Cannot add custom artifact handler and custom lifecycle as a build extension
[
http://jira.codehaus.org/browse/MNG-2831?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Vincent Massol reopened MNG-2831:
-
Jason, I'm reopening as I don't believe it's fixed. I've tried it0115 with
2.0.6-SNAPSHOT from trunk and it's failing. The trick is that it works if you
build BOTH the extension and the project in the same reactor run. If you run
first the extension and THEN the project you'll see it fail.
> Cannot add custom artifact handler and custom lifecycle as a build extension
>
>
> Key: MNG-2831
> URL: http://jira.codehaus.org/browse/MNG-2831
> Project: Maven 2
> Issue Type: Bug
> Components: General
>Affects Versions: 2.0.5
>Reporter: Vincent Massol
> Assigned To: Jason van Zyl
> Fix For: 2.0.6
>
>
> I have an extension registering a custom artifact handler and a custom
> lifecycle against plexus. The project that uses that extension get the
> following error:
> {noformat}
> [DEBUG] Error looking up lifecycle mapping to retrieve optional mojos.
> Lifecycle ID: clean. Error: Component descriptor cannot be found in the
> component repository: org.apache.maven.lifecycle.mapping.LifecycleMappingxar.
> org.codehaus.plexus.component.repository.exception.ComponentLookupException:
> Component descriptor cannot be found in the component repository:
> org.apache.maven.lifecycle.mapping.LifecycleMappingxar.
> at
> org.codehaus.plexus.DefaultPlexusContainer.lookup(DefaultPlexusContainer.java:323)
> at
> org.codehaus.plexus.DefaultPlexusContainer.lookup(DefaultPlexusContainer.java:440)
> at
> org.apache.maven.execution.MavenSession.lookup(MavenSession.java:123)
> at
> org.apache.maven.lifecycle.DefaultLifecycleExecutor.findOptionalMojosForLifecycle(DefaultLifecycleExecutor.java:)
> at
> org.apache.maven.lifecycle.DefaultLifecycleExecutor.bindLifecycleForPackaging(DefaultLifecycleExecutor.java:999)
> at
> org.apache.maven.lifecycle.DefaultLifecycleExecutor.constructLifecycleMappings(DefaultLifecycleExecutor.java:980)
> at
> org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoal(DefaultLifecycleExecutor.java:458)
> at
> org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoalAndHandleFailures(DefaultLifecycleExecutor.java:311)
> at
> org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeTaskSegments(DefaultLifecycleExecutor.java:278)
> at
> org.apache.maven.lifecycle.DefaultLifecycleExecutor.execute(DefaultLifecycleExecutor.java:143)
> at org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:330)
> at org.apache.maven.DefaultMaven.execute(DefaultMaven.java:123)
> at org.apache.maven.cli.MavenCli.main(MavenCli.java:272)
> 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:585)
> 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)
> [DEBUG] Skipping disabled repository codehaus.plugin.snapshots
> [DEBUG] Skipping disabled repository apache.snapshots
> [DEBUG] maven-clean-plugin: resolved to version 2.1 from repository central
> [DEBUG] Retrieving parent-POM:
> org.apache.maven.plugins:maven-plugin-parent::2.0 for project:
> null:maven-clean-plugin:maven-plugin:2.1 from the repository.
> [DEBUG] org.apache.maven.plugins:maven-clean-plugin:maven-plugin:2.1:runtime
> (selected for runtime)
> [DEBUG] org.apache.maven:maven-plugin-api:jar:2.0:runtime (selected for
> runtime)
> [DEBUG] Retrieving parent-POM:
> org.apache.maven.shared:shared-components-parent::1 for project:
> null:file-management:jar:1.0 from the repository.
> [DEBUG] org.apache.maven.shared:file-management:jar:1.0:runtime (selected
> for runtime)
> [DEBUG] org.codehaus.plexus:plexus-utils:jar:1.0.4:runtime (selected for
> runtime)
> [DEBUG] Configuring mojo
> 'org.apache.maven.plugins:maven-clean-plugin:2.1:clean' -->
> [DEBUG] (f) directory =
> /Users/vmassol/dev/maven/trunks/core-integration-testing/core-integration-tests/src/test/resources/it0115-customArtifactHandlerAndCustomLifecycle/test-project/target
> [DEBUG] (f) outputDirectory =
> /Users/vmassol/dev/maven/trunks/core-integration-testing/core-integration-tests/src/test/resources/it0115-customArtifactHandlerAndCustomLifecycle/test-project/target/classes
> [DE
[jira] Created: (MAVENUPLOAD-1423) HtmlUnit 1.11 upload request
HtmlUnit 1.11 upload request Key: MAVENUPLOAD-1423 URL: http://jira.codehaus.org/browse/MAVENUPLOAD-1423 Project: maven-upload-requests Issue Type: Task Reporter: Marc Guillemot http://htmlunit.sourceforge.net/htmlunit-1.11-bundle.jar Team members, including myself: http://htmlunit.sourceforge.net/team-list.html http://sourceforge.net/project/memberlist.php?group_id=47038 -- 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: (MRM-303) 404 Error when trying to access archiva after install
[ http://jira.codehaus.org/browse/MRM-303?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Emmanuel Venisse closed MRM-303. Assignee: Emmanuel Venisse Resolution: Fixed Fix Version/s: 1.0 > 404 Error when trying to access archiva after install > - > > Key: MRM-303 > URL: http://jira.codehaus.org/browse/MRM-303 > Project: Archiva > Issue Type: Bug > Environment: Linux >Reporter: David Bilge > Assigned To: Emmanuel Venisse >Priority: Critical > Fix For: 1.0 > > Attachments: stacktrace.txt > > > I pulled down the latest version of archiva from the svn and built it with > "mvn install". If I run it with the integrated Jetty (mvn jetty:run) I get > the following page as soon as I point my browser to http://host:9091/: > "HTTP ERROR: 404 > Caught Exception while registering Interceptor class > pssEnvironmentCheckInterceptor" > (... - see attachment) > A similar thing happens, if I try to run it via integrated Plexus (this does > not show an exception in the browser but on the console). -- 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: (CONTINUUM-515) Add a wait page when adding a project
[ http://jira.codehaus.org/browse/CONTINUUM-515?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Olivier Lamy updated CONTINUUM-515: --- Attachment: CONTINUUM-515 Patch provided. Do the job for add m2/m1 projects. > Add a wait page when adding a project > - > > Key: CONTINUUM-515 > URL: http://jira.codehaus.org/browse/CONTINUUM-515 > Project: Continuum > Issue Type: Improvement > Components: Web interface >Reporter: Emmanuel Venisse > Fix For: 1.1-alpha-2 > > Attachments: CONTINUUM-515 > > -- 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: (CONTINUUM-515) Add a wait page when adding a project
[ http://jira.codehaus.org/browse/CONTINUUM-515?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_90205 ] Olivier Lamy commented on CONTINUUM-515: Missing binary file iin the patch. It's here http://codehaus.org/~olamy/wait.gif. > Add a wait page when adding a project > - > > Key: CONTINUUM-515 > URL: http://jira.codehaus.org/browse/CONTINUUM-515 > Project: Continuum > Issue Type: Improvement > Components: Web interface >Reporter: Emmanuel Venisse > Fix For: 1.1-alpha-2 > > Attachments: CONTINUUM-515 > > -- 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: (MAVENUPLOAD-1220) Upload mx4j 3.0.2
[ http://jira.codehaus.org/browse/MAVENUPLOAD-1220?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Kevan Miller reopened MAVENUPLOAD-1220: --- mx4j-3.0.2.jar has been released to maven central (http://repo1.maven.org/maven2/mx4j/mx4j/3.0.2/mx4j-3.0.2.jar), but not any of the other mx4j components. Can you push out the rest? mx4j is not a maven generated project. it probably will not ever be. The new 3.0.2 poms are better than the 3.0.1 poms. Geronimo project would appreciate it if you would push the rest of the 3.0.2 artifacts out into central... > Upload mx4j 3.0.2 > - > > Key: MAVENUPLOAD-1220 > URL: http://jira.codehaus.org/browse/MAVENUPLOAD-1220 > Project: maven-upload-requests > Issue Type: Task >Reporter: Kevan Miller > Assigned To: Carlos Sanchez > > The mx4j project has created a service release of mx4j. This release fixes > problems found in Geronimo testing. > I'm not a developer on mx4j, but have exchanged notes with Simone Bordet (who > is). He requested that I submit the upload request. > These new poms and jars mirror the 3.0.1 mx4j poms and jars already on > ibiblio. -- 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: (MAVENUPLOAD-1395) Maven-jlex is a maven plugin for jlex, a lexical analyzer generator for Java.
[ http://jira.codehaus.org/browse/MAVENUPLOAD-1395?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_90208 ] Kevin Conaway commented on MAVENUPLOAD-1395: Fixed the URL. Sorry about the trouble. SF was giving me some trouble. > Maven-jlex is a maven plugin for jlex, a lexical analyzer generator for Java. > - > > Key: MAVENUPLOAD-1395 > URL: http://jira.codehaus.org/browse/MAVENUPLOAD-1395 > Project: maven-upload-requests > Issue Type: Task >Reporter: Kevin Conaway > > http://maven-jlex.sourceforge.net/maven-jlex-plugin-1.0-bundle.jar > http://maven-jlex.sourceforge.net/ > http://maven-jlex.sourceforge.net/team-list.html > Maven-jlex is a maven plugin for jlex, a lexical analyzer generator for Java. > It allows users to integreate the generation of lexical analyzers into the > maven build lifecycle -- 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: (MECLIPSE-241) Compiler settings from parent project aren't used in wtp facet
[
http://jira.codehaus.org/browse/MECLIPSE-241?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Arnaud Heritier reopened MECLIPSE-241:
--
The problem is different. It's because compiler settings are defined in the
pluginManagement par in the pom
> Compiler settings from parent project aren't used in wtp facet
> --
>
> Key: MECLIPSE-241
> URL: http://jira.codehaus.org/browse/MECLIPSE-241
> Project: Maven 2.x Eclipse Plugin
> Issue Type: Bug
> Components: WTP support
>Affects Versions: 2.3
> Environment: maven 2.0.4 / maven 2.0.5
>Reporter: Arnaud Heritier
> Assigned To: Arnaud Heritier
>Priority: Minor
> Fix For: 2.4
>
> Attachments: project-28.zip
>
>
> In a parent POM I have :
> {code:xml}
>
> org.apache.maven.plugins
> maven-compiler-plugin
>
> 1.5
> 1.5
>
>
> {code}
> And I have a submodule (a war) configure to generate wtp 1.5 settings :
> {code:xml}
>
> org.apache.maven.plugins
> maven-eclipse-plugin
>
> 1.5
>
>
> {code}
> After running eclipse:eclipse I have the following in my
> org.eclipse.wst.common.project.facet.core.xml :
> {code:xml}
>
>
>
>
>
>
> {code}
> And not
> {code:xml}
>
>
>
>
>
>
> {code}
--
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: (MECLIPSE-241) Compiler settings in pluginManagement aren't used in wtp facet
[
http://jira.codehaus.org/browse/MECLIPSE-241?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Arnaud Heritier updated MECLIPSE-241:
-
Description:
In a parent POM I have in the pluginManagement part :
{code:xml}
org.apache.maven.plugins
maven-compiler-plugin
1.5
1.5
{code}
And I have a submodule (a war) configure to generate wtp 1.5 settings :
{code:xml}
org.apache.maven.plugins
maven-eclipse-plugin
1.5
{code}
After running eclipse:eclipse I have the following in my
org.eclipse.wst.common.project.facet.core.xml :
{code:xml}
{code}
And not
{code:xml}
{code}
was:
In a parent POM I have :
{code:xml}
org.apache.maven.plugins
maven-compiler-plugin
1.5
1.5
{code}
And I have a submodule (a war) configure to generate wtp 1.5 settings :
{code:xml}
org.apache.maven.plugins
maven-eclipse-plugin
1.5
{code}
After running eclipse:eclipse I have the following in my
org.eclipse.wst.common.project.facet.core.xml :
{code:xml}
{code}
And not
{code:xml}
{code}
Summary: Compiler settings in pluginManagement aren't used in wtp facet
(was: Compiler settings from parent project aren't used in wtp facet)
> Compiler settings in pluginManagement aren't used in wtp facet
> --
>
> Key: MECLIPSE-241
> URL: http://jira.codehaus.org/browse/MECLIPSE-241
> Project: Maven 2.x Eclipse Plugin
> Issue Type: Bug
> Components: WTP support
>Affects Versions: 2.3
> Environment: maven 2.0.4 / maven 2.0.5
>Reporter: Arnaud Heritier
> Assigned To: Arnaud Heritier
>Priority: Minor
> Fix For: 2.4
>
> Attachments: project-28.zip
>
>
> In a parent POM I have in the pluginManagement part :
> {code:xml}
>
> org.apache.maven.plugins
> maven-compiler-plugin
>
> 1.5
> 1.5
>
>
> {code}
> And I have a submodule (a war) configure to generate wtp 1.5 settings :
> {code:xml}
>
> org.apache.maven.plugins
> maven-eclipse-plugin
>
> 1.5
>
>
> {code}
> After running eclipse:eclipse I have the following in my
> org.eclipse.wst.common.project.facet.core.xml :
> {code:xml}
>
>
>
>
>
>
> {code}
> And not
> {code:xml}
>
>
>
>
>
>
> {code}
--
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: (MNG-2831) Cannot add custom artifact handler and custom lifecycle as a build extension
[
http://jira.codehaus.org/browse/MNG-2831?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_90211
]
Jason van Zyl commented on MNG-2831:
Did you run the integration test? As there is no reactor in the IT, the
projects are being run separately and not in a reactor and it passes.
> Cannot add custom artifact handler and custom lifecycle as a build extension
>
>
> Key: MNG-2831
> URL: http://jira.codehaus.org/browse/MNG-2831
> Project: Maven 2
> Issue Type: Bug
> Components: General
>Affects Versions: 2.0.5
>Reporter: Vincent Massol
> Assigned To: Jason van Zyl
> Fix For: 2.0.6
>
>
> I have an extension registering a custom artifact handler and a custom
> lifecycle against plexus. The project that uses that extension get the
> following error:
> {noformat}
> [DEBUG] Error looking up lifecycle mapping to retrieve optional mojos.
> Lifecycle ID: clean. Error: Component descriptor cannot be found in the
> component repository: org.apache.maven.lifecycle.mapping.LifecycleMappingxar.
> org.codehaus.plexus.component.repository.exception.ComponentLookupException:
> Component descriptor cannot be found in the component repository:
> org.apache.maven.lifecycle.mapping.LifecycleMappingxar.
> at
> org.codehaus.plexus.DefaultPlexusContainer.lookup(DefaultPlexusContainer.java:323)
> at
> org.codehaus.plexus.DefaultPlexusContainer.lookup(DefaultPlexusContainer.java:440)
> at
> org.apache.maven.execution.MavenSession.lookup(MavenSession.java:123)
> at
> org.apache.maven.lifecycle.DefaultLifecycleExecutor.findOptionalMojosForLifecycle(DefaultLifecycleExecutor.java:)
> at
> org.apache.maven.lifecycle.DefaultLifecycleExecutor.bindLifecycleForPackaging(DefaultLifecycleExecutor.java:999)
> at
> org.apache.maven.lifecycle.DefaultLifecycleExecutor.constructLifecycleMappings(DefaultLifecycleExecutor.java:980)
> at
> org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoal(DefaultLifecycleExecutor.java:458)
> at
> org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoalAndHandleFailures(DefaultLifecycleExecutor.java:311)
> at
> org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeTaskSegments(DefaultLifecycleExecutor.java:278)
> at
> org.apache.maven.lifecycle.DefaultLifecycleExecutor.execute(DefaultLifecycleExecutor.java:143)
> at org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:330)
> at org.apache.maven.DefaultMaven.execute(DefaultMaven.java:123)
> at org.apache.maven.cli.MavenCli.main(MavenCli.java:272)
> 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:585)
> 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)
> [DEBUG] Skipping disabled repository codehaus.plugin.snapshots
> [DEBUG] Skipping disabled repository apache.snapshots
> [DEBUG] maven-clean-plugin: resolved to version 2.1 from repository central
> [DEBUG] Retrieving parent-POM:
> org.apache.maven.plugins:maven-plugin-parent::2.0 for project:
> null:maven-clean-plugin:maven-plugin:2.1 from the repository.
> [DEBUG] org.apache.maven.plugins:maven-clean-plugin:maven-plugin:2.1:runtime
> (selected for runtime)
> [DEBUG] org.apache.maven:maven-plugin-api:jar:2.0:runtime (selected for
> runtime)
> [DEBUG] Retrieving parent-POM:
> org.apache.maven.shared:shared-components-parent::1 for project:
> null:file-management:jar:1.0 from the repository.
> [DEBUG] org.apache.maven.shared:file-management:jar:1.0:runtime (selected
> for runtime)
> [DEBUG] org.codehaus.plexus:plexus-utils:jar:1.0.4:runtime (selected for
> runtime)
> [DEBUG] Configuring mojo
> 'org.apache.maven.plugins:maven-clean-plugin:2.1:clean' -->
> [DEBUG] (f) directory =
> /Users/vmassol/dev/maven/trunks/core-integration-testing/core-integration-tests/src/test/resources/it0115-customArtifactHandlerAndCustomLifecycle/test-project/target
> [DEBUG] (f) outputDirectory =
> /Users/vmassol/dev/maven/trunks/core-integration-testing/core-integration-tests/src/test/resources/it0115-customArtifactHandlerAndCustomLifecycle/test-project/target/classes
> [DEBUG] (f) testOutputDirectory =
> /Users/vmassol/dev/maven/trunks/core-integration-testing/core-integration-tests/src/test/resou
[jira] Closed: (MECLIPSE-241) Compiler settings in pluginManagement aren't used in wtp facet
[
http://jira.codehaus.org/browse/MECLIPSE-241?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Arnaud Heritier closed MECLIPSE-241.
Resolution: Fixed
Fixed
> Compiler settings in pluginManagement aren't used in wtp facet
> --
>
> Key: MECLIPSE-241
> URL: http://jira.codehaus.org/browse/MECLIPSE-241
> Project: Maven 2.x Eclipse Plugin
> Issue Type: Bug
> Components: WTP support
>Affects Versions: 2.3
> Environment: maven 2.0.4 / maven 2.0.5
>Reporter: Arnaud Heritier
> Assigned To: Arnaud Heritier
>Priority: Minor
> Fix For: 2.4
>
> Attachments: project-28.zip
>
>
> In a parent POM I have in the pluginManagement part :
> {code:xml}
>
> org.apache.maven.plugins
> maven-compiler-plugin
>
> 1.5
> 1.5
>
>
> {code}
> And I have a submodule (a war) configure to generate wtp 1.5 settings :
> {code:xml}
>
> org.apache.maven.plugins
> maven-eclipse-plugin
>
> 1.5
>
>
> {code}
> After running eclipse:eclipse I have the following in my
> org.eclipse.wst.common.project.facet.core.xml :
> {code:xml}
>
>
>
>
>
>
> {code}
> And not
> {code:xml}
>
>
>
>
>
>
> {code}
--
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] Work started: (MECLIPSE-215) WTP 1.5 Documentation
[ http://jira.codehaus.org/browse/MECLIPSE-215?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Work on MECLIPSE-215 started by Arnaud Heritier. > WTP 1.5 Documentation > - > > Key: MECLIPSE-215 > URL: http://jira.codehaus.org/browse/MECLIPSE-215 > Project: Maven 2.x Eclipse Plugin > Issue Type: Bug > Components: WTP support >Affects Versions: 2.3 >Reporter: Shelley L > Assigned To: Arnaud Heritier >Priority: Minor > Fix For: 2.4 > > > The maven-eclipse-plugin mojo documentation should be updated to mention WTP > 1.5 support. Currently, the wtpversion parameter description states that the > only supported versions are "R7" and "1.0." > http://maven.apache.org/plugins/maven-eclipse-plugin/eclipse-mojo.html -- 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: (MECLIPSE-215) WTP 1.5 Documentation
[ http://jira.codehaus.org/browse/MECLIPSE-215?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Arnaud Heritier closed MECLIPSE-215. Resolution: Fixed Fix Version/s: 2.4 Fixed. Will be updated in the next site deployment > WTP 1.5 Documentation > - > > Key: MECLIPSE-215 > URL: http://jira.codehaus.org/browse/MECLIPSE-215 > Project: Maven 2.x Eclipse Plugin > Issue Type: Bug > Components: WTP support >Affects Versions: 2.3 >Reporter: Shelley L > Assigned To: Arnaud Heritier >Priority: Minor > Fix For: 2.4 > > > The maven-eclipse-plugin mojo documentation should be updated to mention WTP > 1.5 support. Currently, the wtpversion parameter description states that the > only supported versions are "R7" and "1.0." > http://maven.apache.org/plugins/maven-eclipse-plugin/eclipse-mojo.html -- 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: (MECLIPSE-243) The last 2.4 SNAPSHOT forbid Apache Directory Server to be built
[ http://jira.codehaus.org/browse/MECLIPSE-243?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_90214 ] Arnaud Heritier commented on MECLIPSE-243: -- I had the same error yesterday. It's a problem with the build of this plugin. We use this test version, in theory, only for our tests But it's not the case actually. It should be fixed actually. I redeployed it (and I skip tests) > The last 2.4 SNAPSHOT forbid Apache Directory Server to be built > > > Key: MECLIPSE-243 > URL: http://jira.codehaus.org/browse/MECLIPSE-243 > Project: Maven 2.x Eclipse Plugin > Issue Type: Bug >Affects Versions: 2.4 >Reporter: Emmanuel Lécharny >Priority: Blocker > Fix For: 2.4 > > > We can't anymore build ADS since a new version (SNAPSHOT-2.4) has been pushed > on the http://people.apache.org/repo/m2-snapshot-repository repo. > If I switch the version to 2.3 by declaring it in the PluginManagement, > everything is fine. I'm using Maven 2.0.5 > Here is the log : > [EMAIL PROTECTED] apacheds-trunks]$ mvn -X eclipse:eclipse > + Error stacktraces are turned on. > Maven version: 2.0.5 > [DEBUG] Building Maven user-level plugin registry from: > '/home/elecharny/.m2/plugin-registry.xml' > [DEBUG] Building Maven global-level plugin registry from: > '/opt/maven-2.0.5/conf/plugin-registry.xml' > [INFO] Scanning for projects... > [INFO] Reactor build order: > [INFO] Apache Directory Build > [INFO] Apache Directory Shared > [INFO] Apache Directory ASN.1 Shared > [INFO] Apache Directory Protocol Ldap Shared > [INFO] ApacheDS > [INFO] ApacheDS Constants > [INFO] ApacheDS Core Shared > [INFO] ApacheDS Schema Registries > [INFO] ApacheDS BTree Base > [INFO] ApacheDS JDBM Store > [INFO] ApacheDS Utils > [INFO] ApacheDS Core Plugin (Maven 2) > [INFO] ApacheDS Bootstrap Schemas > [INFO] ApacheDS Extra Schemas > [INFO] ApacheDS Bootstrap Plugin > [INFO] ApacheDS Bootstrap Partition > [INFO] ApacheDS Core > [INFO] ApacheDS Core Unit > [INFO] ApacheDS Protocol Shared > [INFO] ApacheDS Protocol Ntp > [INFO] Apache Directory MINA ASN.1 Codec Shared > [INFO] ApacheDS Protocol Ldap > [INFO] ApacheDS Protocol Kerberos Shared > [INFO] ApacheDS Protocol Kerberos > [INFO] ApacheDS Protocol Dhcp > [INFO] ApacheDS Protocol Dns > [INFO] ApacheDS Protocol Change Password > [INFO] ApacheDS Server JNDI > [INFO] ApacheDS Server Unit > [INFO] ApacheDS Server SSL > [INFO] Apache Directory Daemon > [INFO] Apache Directory Daemon Bootstrappers > [INFO] ApacheDS Server Main > [INFO] ApacheDS Server Tools > [INFO] ApacheDS replication > [INFO] ApacheDS Server Replication Service > [INFO] Apache Directory Protocol Ldap Converters > [INFO] Apache Directory Daemon Plugin (Maven 2) > [INFO] Searching repository for plugin with prefix: 'eclipse'. > [DEBUG] maven-eclipse-plugin: resolved to version 2.4-SNAPSHOT from > repository central > [DEBUG] Skipping disabled repository central > [DEBUG] maven-eclipse-plugin: resolved to version 2.4-20070315.175923-5 from > repository apache.snapshots > [DEBUG] Retrieving parent-POM: org.apache.maven.plugins:maven-plugins::8 for > project: > org.apache.maven.plugins:maven-eclipse-plugin:maven-plugin:2.4-SNAPSHOT from > the repository. > [DEBUG] Retrieving parent-POM: org.apache.maven:maven-parent::5 for project: > org.apache.maven.plugins:maven-plugins:pom:8 from the repository. > [DEBUG] Retrieving parent-POM: org.apache:apache::3 for project: > org.apache.maven:maven-parent:pom:5 from the repository. > [DEBUG] Retrieving parent-POM: org.apache.maven.plugins:maven-plugins::8 for > project: > org.apache.maven.plugins:maven-eclipse-plugin:maven-plugin:2.4-SNAPSHOT from > the repository. > [DEBUG] Retrieving parent-POM: org.apache.maven:maven-parent::5 for project: > org.apache.maven.plugins:maven-plugins:pom:8 from the repository. > [DEBUG] Retrieving parent-POM: org.apache:apache::3 for project: > org.apache.maven:maven-parent:pom:5 from the repository. > [DEBUG] Retrieving parent-POM: org.apache.maven.plugins:maven-plugins::8 for > project: > org.apache.maven.plugins:maven-eclipse-plugin:maven-plugin:2.4-SNAPSHOT from > the repository. > [DEBUG] Retrieving parent-POM: org.apache.maven:maven-parent::5 for project: > org.apache.maven.plugins:maven-plugins:pom:8 from the repository. > [DEBUG] Retrieving parent-POM: org.apache:apache::3 for project: > org.apache.maven:maven-parent:pom:5 from the repository. > [INFO] > > [INFO] Building Apache Directory Build > [INFO]task-segment: [eclipse:eclipse] > [INFO] > > [INFO] Preparing eclipse:eclipse > [DEBUG] Sk
[jira] Commented: (MECLIPSE-107) Dependency Version Incorrectly Taken from DependencyManagement
[ http://jira.codehaus.org/browse/MECLIPSE-107?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_90215 ] Arnaud Heritier commented on MECLIPSE-107: -- The snapshot I just deployed should have fixed this bug. Can you verify please ? > Dependency Version Incorrectly Taken from DependencyManagement > -- > > Key: MECLIPSE-107 > URL: http://jira.codehaus.org/browse/MECLIPSE-107 > Project: Maven 2.x Eclipse Plugin > Issue Type: Bug > Components: dependency resolution >Affects Versions: 2.2 >Reporter: Stephen Duncan Jr >Priority: Critical > Attachments: dmtest.zip, > MECLIPSE-107-maven-eclipse-plugin-20061211-1200.patch > > > The version used when generating .classpath is taken from > dependencyManagement even though the child pom sets the dependency version, > which should override what is in dependencyManagement. This is a regression > from the correct behaviour in 2.1. > The attached project demonstrates the problem. The .classpath file generated > for the "child" project should specify log4j-1.2.13, but instead specifies > 1.28. -- 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: (MGPG-4) Invalid signature on installed or deployed POM
Invalid signature on installed or deployed POM -- Key: MGPG-4 URL: http://jira.codehaus.org/browse/MGPG-4 Project: Maven 2.x GPG Plugin Issue Type: Bug Reporter: Jeremy Boynes The signature on the POM installed in the local or remote repo is bad. The one on the pom in the target directory is good. Presumably the plugin should be signing the regenerated POM rather than the original. -- 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: (MECLIPSE-65) Add contextName parameter to eclipse mojo so a webtool context name doesn't have to match artifactId/project name.
[ http://jira.codehaus.org/browse/MECLIPSE-65?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_90221 ] Dan Tran commented on MECLIPSE-65: -- Can we have this applied? :-) > Add contextName parameter to eclipse mojo so a webtool context name doesn't > have to match artifactId/project name. > -- > > Key: MECLIPSE-65 > URL: http://jira.codehaus.org/browse/MECLIPSE-65 > Project: Maven 2.x Eclipse Plugin > Issue Type: New Feature > Components: WTP support >Reporter: Yujin Kim > Assigned To: Edwin Punzalan >Priority: Minor > Attachments: MECLIPSE-65-PATCH.txt, MECLIPSE-65.patch > > -- 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: (MAVENUPLOAD-1220) Upload mx4j 3.0.2
[ http://jira.codehaus.org/browse/MAVENUPLOAD-1220?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_90226 ] Carlos Sanchez commented on MAVENUPLOAD-1220: - can't you say what the dependencies are? you should know better than me how they relate to each other > Upload mx4j 3.0.2 > - > > Key: MAVENUPLOAD-1220 > URL: http://jira.codehaus.org/browse/MAVENUPLOAD-1220 > Project: maven-upload-requests > Issue Type: Task >Reporter: Kevan Miller > Assigned To: Carlos Sanchez > > The mx4j project has created a service release of mx4j. This release fixes > problems found in Geronimo testing. > I'm not a developer on mx4j, but have exchanged notes with Simone Bordet (who > is). He requested that I submit the upload request. > These new poms and jars mirror the 3.0.1 mx4j poms and jars already on > ibiblio. -- 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: (MAVENUPLOAD-1220) Upload mx4j 3.0.2
[ http://jira.codehaus.org/browse/MAVENUPLOAD-1220?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_90227 ] Jason Dillon commented on MAVENUPLOAD-1220: --- Why do we need dependencies in here? I suppose the mx4j team would know much better how they relate. I only know that G 1.2 needs: * mx4j:mx4j * mx4j:mx4j-remote Some places modules need one, some need both... short of that I have not idea. And I'm not sure Kevan knows either... we would just be guessing and would probably end up with a skewed list anyways. Can we please just get the artifacts+poms published to central as they are attached in the bundles? > Upload mx4j 3.0.2 > - > > Key: MAVENUPLOAD-1220 > URL: http://jira.codehaus.org/browse/MAVENUPLOAD-1220 > Project: maven-upload-requests > Issue Type: Task >Reporter: Kevan Miller > Assigned To: Carlos Sanchez > > The mx4j project has created a service release of mx4j. This release fixes > problems found in Geronimo testing. > I'm not a developer on mx4j, but have exchanged notes with Simone Bordet (who > is). He requested that I submit the upload request. > These new poms and jars mirror the 3.0.1 mx4j poms and jars already on > ibiblio. -- 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: (MAVENUPLOAD-1220) Upload mx4j 3.0.2
[ http://jira.codehaus.org/browse/MAVENUPLOAD-1220?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Carlos Sanchez updated MAVENUPLOAD-1220: Attachment: dep.png Now you have the dependencies For the war just look into WEB-INF/lib For the circular ep i guess impl depends on jmx Any other questions try to ask the developers > Upload mx4j 3.0.2 > - > > Key: MAVENUPLOAD-1220 > URL: http://jira.codehaus.org/browse/MAVENUPLOAD-1220 > Project: maven-upload-requests > Issue Type: Task >Reporter: Kevan Miller > Assigned To: Carlos Sanchez > Attachments: dep.png > > > The mx4j project has created a service release of mx4j. This release fixes > problems found in Geronimo testing. > I'm not a developer on mx4j, but have exchanged notes with Simone Bordet (who > is). He requested that I submit the upload request. > These new poms and jars mirror the 3.0.1 mx4j poms and jars already on > ibiblio. -- 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: (CONTINUUM-1155) Continuum should be able to use cached username/password credentials when the scm provider supports it
[ http://jira.codehaus.org/browse/CONTINUUM-1155?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Teodoro Cue Jr. updated CONTINUUM-1155: --- Attachment: CONTINUUM-1155-continuum-webapp.patch Copied Lester's solution and implemented it on other project types. > Continuum should be able to use cached username/password credentials when the > scm provider supports it > -- > > Key: CONTINUUM-1155 > URL: http://jira.codehaus.org/browse/CONTINUUM-1155 > Project: Continuum > Issue Type: New Feature > Components: Environmental >Affects Versions: 1.0.3 >Reporter: Edwin Punzalan > Assigned To: Lester Ecarma > Fix For: 1.1-alpha-# > > Attachments: CONTINUUM-1155-continuum-webapp.patch, > CONTINUUM-1155.patch > > -- 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: (MAVENUPLOAD-1220) Upload mx4j 3.0.2
[ http://jira.codehaus.org/browse/MAVENUPLOAD-1220?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_90231 ] Jason Dillon commented on MAVENUPLOAD-1220: --- So, I take it you'd like us to re-roll the bundles with deps matching the graph you made/attached? What did you use to make that btw? > Upload mx4j 3.0.2 > - > > Key: MAVENUPLOAD-1220 > URL: http://jira.codehaus.org/browse/MAVENUPLOAD-1220 > Project: maven-upload-requests > Issue Type: Task >Reporter: Kevan Miller > Assigned To: Carlos Sanchez > Attachments: dep.png > > > The mx4j project has created a service release of mx4j. This release fixes > problems found in Geronimo testing. > I'm not a developer on mx4j, but have exchanged notes with Simone Bordet (who > is). He requested that I submit the upload request. > These new poms and jars mirror the 3.0.1 mx4j poms and jars already on > ibiblio. -- 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: (MAVENUPLOAD-1220) Upload mx4j 3.0.2
[
http://jira.codehaus.org/browse/MAVENUPLOAD-1220?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_90232
]
Jason Dillon commented on MAVENUPLOAD-1220:
---
Hrm... upon closer inspection of what is actually in these jars... I'm not
really sure that it is such a good idea to put in any dependencies in the pom.
>From their {{README.txt}}:
{quote}
+ mx4j-jmx.jar --> contains the JSR 3 javax.management.* classes
+ mx4j-impl.jar --> contains the mx4j.* classes that implements JSR 3
functionalities
+ mx4j.jar --> The mx4j-jmx.jar and mx4j-impl.jar packed together
+ mx4j-rjmx.jar --> contains the JSR 160 javax.management.remote.* classes
+ mx4j-rimpl.jar --> contains the mx4j.* classes that implements JSR 160
functionalities
+ mx4j-remote.jar--> The mx4j-rjmx.jar and mx4j-rimpl.jar packed together
+ mx4j-tools.jar --> contains the MX4J tools
+ mx4j-soap.war --> contains a sample web application that deploys a JSR
160 connector server over the soap protocol
+ mx4j-examples.jar --> contains the MX4J examples
{quote}
Based on this I don't believe that these artifacts need (or should have any
deps in the pom)... the reasoning behind this is that users may want to select
which jar they depend up.
For example, mx4j-tools.jar users may want to depend on mx4j.jar or
(mx4j-jmx.jar and mx4j-impl.jar), and *some* of the tools may also depend on
some of the remote classes, which could be in mx4j-remote.jar or (mx4j-rjmx.jar
and mx4j-rimpl.jar).
The mx4j-soap.war has all of the deps included, so it does not need any deps,
since they are included in WEB-INF/lib.
And mx4j-examples.jar has similar issues as mx4j-tools.jar does... in that
there are a few different ways to pick up the artifacts.
BTW, the graph attached is not really accurate, since it shows that mx4j-rimpl
and mx4j-rjmx depend on mx4j-remote, when mx4j-remote is an aggregation of the
contents of both of those jars. Same for mx4j-jmx and mx4j-impl.
Based on this... I don't think any dependencies should be added to these jars
and that they should be deployed to central ASIS in their bundled form here:
http://people.apache.org/~kevan/Mx4jUploadRequests
* * *
If that is not acceptable, then please advise what would be acceptable... as
based on the jars contents I don't see an obvious way to roll the dependencies.
Doing so makes some decisions for users which I am not sure we should be doing.
If mx4j was built with maven, perhaps it would reduce the number of jars with
duplicate classes and use the maven2 transitive dependency mechanism. But I
don't see that happening anytime soon... and its certainly not going to happen
for this release.
I have ping'd the mx4j dev list to enlist any advise they may have... but IMO I
think that the artifacts should be published how they are currently bundled
with no dependencies.
> Upload mx4j 3.0.2
> -
>
> Key: MAVENUPLOAD-1220
> URL: http://jira.codehaus.org/browse/MAVENUPLOAD-1220
> Project: maven-upload-requests
> Issue Type: Task
>Reporter: Kevan Miller
> Assigned To: Carlos Sanchez
> Attachments: dep.png
>
>
> The mx4j project has created a service release of mx4j. This release fixes
> problems found in Geronimo testing.
> I'm not a developer on mx4j, but have exchanged notes with Simone Bordet (who
> is). He requested that I submit the upload request.
> These new poms and jars mirror the 3.0.1 mx4j poms and jars already on
> ibiblio.
--
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: (MNG-2831) Cannot add custom artifact handler and custom lifecycle as a build extension
[
http://jira.codehaus.org/browse/MNG-2831?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_90234
]
Vincent Massol commented on MNG-2831:
-
What I did:
{noformat}
$ cd it0115-customArtifactHandlerAndCustomLifecycle/
$ cd test-extension/
$ mvn install
$ cd ../test-project/
$ mvn install <--- fails
{noformat}
The error is:
{noformat}
[INFO]
[INFO] Building Test Project
[INFO]task-segment: [install]
[INFO]
[INFO]
[ERROR] BUILD ERROR
[INFO]
[INFO] Cannot find lifecycle mapping for packaging: 'xar'.
Component descriptor cannot be found in the component repository:
org.apache.maven.lifecycle.mapping.LifecycleMappingxar.
{noformat}
Are you able to reproduce this?
> Cannot add custom artifact handler and custom lifecycle as a build extension
>
>
> Key: MNG-2831
> URL: http://jira.codehaus.org/browse/MNG-2831
> Project: Maven 2
> Issue Type: Bug
> Components: General
>Affects Versions: 2.0.5
>Reporter: Vincent Massol
> Assigned To: Jason van Zyl
> Fix For: 2.0.6
>
>
> I have an extension registering a custom artifact handler and a custom
> lifecycle against plexus. The project that uses that extension get the
> following error:
> {noformat}
> [DEBUG] Error looking up lifecycle mapping to retrieve optional mojos.
> Lifecycle ID: clean. Error: Component descriptor cannot be found in the
> component repository: org.apache.maven.lifecycle.mapping.LifecycleMappingxar.
> org.codehaus.plexus.component.repository.exception.ComponentLookupException:
> Component descriptor cannot be found in the component repository:
> org.apache.maven.lifecycle.mapping.LifecycleMappingxar.
> at
> org.codehaus.plexus.DefaultPlexusContainer.lookup(DefaultPlexusContainer.java:323)
> at
> org.codehaus.plexus.DefaultPlexusContainer.lookup(DefaultPlexusContainer.java:440)
> at
> org.apache.maven.execution.MavenSession.lookup(MavenSession.java:123)
> at
> org.apache.maven.lifecycle.DefaultLifecycleExecutor.findOptionalMojosForLifecycle(DefaultLifecycleExecutor.java:)
> at
> org.apache.maven.lifecycle.DefaultLifecycleExecutor.bindLifecycleForPackaging(DefaultLifecycleExecutor.java:999)
> at
> org.apache.maven.lifecycle.DefaultLifecycleExecutor.constructLifecycleMappings(DefaultLifecycleExecutor.java:980)
> at
> org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoal(DefaultLifecycleExecutor.java:458)
> at
> org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoalAndHandleFailures(DefaultLifecycleExecutor.java:311)
> at
> org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeTaskSegments(DefaultLifecycleExecutor.java:278)
> at
> org.apache.maven.lifecycle.DefaultLifecycleExecutor.execute(DefaultLifecycleExecutor.java:143)
> at org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:330)
> at org.apache.maven.DefaultMaven.execute(DefaultMaven.java:123)
> at org.apache.maven.cli.MavenCli.main(MavenCli.java:272)
> 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:585)
> 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)
> [DEBUG] Skipping disabled repository codehaus.plugin.snapshots
> [DEBUG] Skipping disabled repository apache.snapshots
> [DEBUG] maven-clean-plugin: resolved to version 2.1 from repository central
> [DEBUG] Retrieving parent-POM:
> org.apache.maven.plugins:maven-plugin-parent::2.0 for project:
> null:maven-clean-plugin:maven-plugin:2.1 from the repository.
> [DEBUG] org.apache.maven.plugins:maven-clean-plugin:maven-plugin:2.1:runtime
> (selected for runtime)
> [DEBUG] org.apache.maven:maven-plugin-api:jar:2.0:runtime (selected for
> runtime)
> [DEBUG] Retrieving parent-POM:
> org.apache.maven.shared:shared-components-parent::1 for project:
> null:file-management:jar:1.0 from the repository.
> [DEBUG] org.apache.maven.shared:file-management:jar:1.0:runtime (selected
> for runtime)
> [DEBUG] org.codehaus.pl
[jira] Commented: (MNG-468) ability to consistently apply a toolchain across plugins
[ http://jira.codehaus.org/browse/MNG-468?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_90235 ] Milos Kleint commented on MNG-468: -- can we increase priority of this one? > ability to consistently apply a toolchain across plugins > > > Key: MNG-468 > URL: http://jira.codehaus.org/browse/MNG-468 > Project: Maven 2 > Issue Type: New Feature >Reporter: Brett Porter > Assigned To: Jason van Zyl >Priority: Minor > Fix For: 2.1.x > > Attachments: build.properties, project.properties > > > for things like the JDK, it may be desirable to compile, jar etc. across the > board with a particular version of the toolchain, other than the one > currently executing. It would be good to be able to configure this location > in the settings.xml and have the plugins use it, forking the compiler, using > a particular runtime, and generating an appropriate manifest. > This is likely to be relevant to other languages too. -- 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: (MNG-2831) Cannot add custom artifact handler and custom lifecycle as a build extension
[
http://jira.codehaus.org/browse/MNG-2831?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jason van Zyl updated MNG-2831:
---
Fix Version/s: (was: 2.0.6)
2.1-alpha-1
> Cannot add custom artifact handler and custom lifecycle as a build extension
>
>
> Key: MNG-2831
> URL: http://jira.codehaus.org/browse/MNG-2831
> Project: Maven 2
> Issue Type: Bug
> Components: General
>Affects Versions: 2.0.5
>Reporter: Vincent Massol
> Assigned To: Jason van Zyl
> Fix For: 2.1-alpha-1
>
>
> I have an extension registering a custom artifact handler and a custom
> lifecycle against plexus. The project that uses that extension get the
> following error:
> {noformat}
> [DEBUG] Error looking up lifecycle mapping to retrieve optional mojos.
> Lifecycle ID: clean. Error: Component descriptor cannot be found in the
> component repository: org.apache.maven.lifecycle.mapping.LifecycleMappingxar.
> org.codehaus.plexus.component.repository.exception.ComponentLookupException:
> Component descriptor cannot be found in the component repository:
> org.apache.maven.lifecycle.mapping.LifecycleMappingxar.
> at
> org.codehaus.plexus.DefaultPlexusContainer.lookup(DefaultPlexusContainer.java:323)
> at
> org.codehaus.plexus.DefaultPlexusContainer.lookup(DefaultPlexusContainer.java:440)
> at
> org.apache.maven.execution.MavenSession.lookup(MavenSession.java:123)
> at
> org.apache.maven.lifecycle.DefaultLifecycleExecutor.findOptionalMojosForLifecycle(DefaultLifecycleExecutor.java:)
> at
> org.apache.maven.lifecycle.DefaultLifecycleExecutor.bindLifecycleForPackaging(DefaultLifecycleExecutor.java:999)
> at
> org.apache.maven.lifecycle.DefaultLifecycleExecutor.constructLifecycleMappings(DefaultLifecycleExecutor.java:980)
> at
> org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoal(DefaultLifecycleExecutor.java:458)
> at
> org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoalAndHandleFailures(DefaultLifecycleExecutor.java:311)
> at
> org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeTaskSegments(DefaultLifecycleExecutor.java:278)
> at
> org.apache.maven.lifecycle.DefaultLifecycleExecutor.execute(DefaultLifecycleExecutor.java:143)
> at org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:330)
> at org.apache.maven.DefaultMaven.execute(DefaultMaven.java:123)
> at org.apache.maven.cli.MavenCli.main(MavenCli.java:272)
> 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:585)
> 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)
> [DEBUG] Skipping disabled repository codehaus.plugin.snapshots
> [DEBUG] Skipping disabled repository apache.snapshots
> [DEBUG] maven-clean-plugin: resolved to version 2.1 from repository central
> [DEBUG] Retrieving parent-POM:
> org.apache.maven.plugins:maven-plugin-parent::2.0 for project:
> null:maven-clean-plugin:maven-plugin:2.1 from the repository.
> [DEBUG] org.apache.maven.plugins:maven-clean-plugin:maven-plugin:2.1:runtime
> (selected for runtime)
> [DEBUG] org.apache.maven:maven-plugin-api:jar:2.0:runtime (selected for
> runtime)
> [DEBUG] Retrieving parent-POM:
> org.apache.maven.shared:shared-components-parent::1 for project:
> null:file-management:jar:1.0 from the repository.
> [DEBUG] org.apache.maven.shared:file-management:jar:1.0:runtime (selected
> for runtime)
> [DEBUG] org.codehaus.plexus:plexus-utils:jar:1.0.4:runtime (selected for
> runtime)
> [DEBUG] Configuring mojo
> 'org.apache.maven.plugins:maven-clean-plugin:2.1:clean' -->
> [DEBUG] (f) directory =
> /Users/vmassol/dev/maven/trunks/core-integration-testing/core-integration-tests/src/test/resources/it0115-customArtifactHandlerAndCustomLifecycle/test-project/target
> [DEBUG] (f) outputDirectory =
> /Users/vmassol/dev/maven/trunks/core-integration-testing/core-integration-tests/src/test/resources/it0115-customArtifactHandlerAndCustomLifecycle/test-project/target/classes
> [DEBUG] (f) testOutputDirectory =
> /Users/vmassol/dev/maven/trunks/core-integration-testing/core-integration-tests/src/test/resources/it0115-customArtifactHandlerAndCustomLifecycle/test-project/target/test-classes
> [DEBUG] --
[jira] Commented: (MNG-2831) Cannot add custom artifact handler and custom lifecycle as a build extension
[
http://jira.codehaus.org/browse/MNG-2831?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_90236
]
Jason van Zyl commented on MNG-2831:
I was actually using 2.1 after looking at my logs. So it works on trunk, not
with 2.0.6.
> Cannot add custom artifact handler and custom lifecycle as a build extension
>
>
> Key: MNG-2831
> URL: http://jira.codehaus.org/browse/MNG-2831
> Project: Maven 2
> Issue Type: Bug
> Components: General
>Affects Versions: 2.0.5
>Reporter: Vincent Massol
> Assigned To: Jason van Zyl
> Fix For: 2.1-alpha-1
>
>
> I have an extension registering a custom artifact handler and a custom
> lifecycle against plexus. The project that uses that extension get the
> following error:
> {noformat}
> [DEBUG] Error looking up lifecycle mapping to retrieve optional mojos.
> Lifecycle ID: clean. Error: Component descriptor cannot be found in the
> component repository: org.apache.maven.lifecycle.mapping.LifecycleMappingxar.
> org.codehaus.plexus.component.repository.exception.ComponentLookupException:
> Component descriptor cannot be found in the component repository:
> org.apache.maven.lifecycle.mapping.LifecycleMappingxar.
> at
> org.codehaus.plexus.DefaultPlexusContainer.lookup(DefaultPlexusContainer.java:323)
> at
> org.codehaus.plexus.DefaultPlexusContainer.lookup(DefaultPlexusContainer.java:440)
> at
> org.apache.maven.execution.MavenSession.lookup(MavenSession.java:123)
> at
> org.apache.maven.lifecycle.DefaultLifecycleExecutor.findOptionalMojosForLifecycle(DefaultLifecycleExecutor.java:)
> at
> org.apache.maven.lifecycle.DefaultLifecycleExecutor.bindLifecycleForPackaging(DefaultLifecycleExecutor.java:999)
> at
> org.apache.maven.lifecycle.DefaultLifecycleExecutor.constructLifecycleMappings(DefaultLifecycleExecutor.java:980)
> at
> org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoal(DefaultLifecycleExecutor.java:458)
> at
> org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoalAndHandleFailures(DefaultLifecycleExecutor.java:311)
> at
> org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeTaskSegments(DefaultLifecycleExecutor.java:278)
> at
> org.apache.maven.lifecycle.DefaultLifecycleExecutor.execute(DefaultLifecycleExecutor.java:143)
> at org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:330)
> at org.apache.maven.DefaultMaven.execute(DefaultMaven.java:123)
> at org.apache.maven.cli.MavenCli.main(MavenCli.java:272)
> 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:585)
> 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)
> [DEBUG] Skipping disabled repository codehaus.plugin.snapshots
> [DEBUG] Skipping disabled repository apache.snapshots
> [DEBUG] maven-clean-plugin: resolved to version 2.1 from repository central
> [DEBUG] Retrieving parent-POM:
> org.apache.maven.plugins:maven-plugin-parent::2.0 for project:
> null:maven-clean-plugin:maven-plugin:2.1 from the repository.
> [DEBUG] org.apache.maven.plugins:maven-clean-plugin:maven-plugin:2.1:runtime
> (selected for runtime)
> [DEBUG] org.apache.maven:maven-plugin-api:jar:2.0:runtime (selected for
> runtime)
> [DEBUG] Retrieving parent-POM:
> org.apache.maven.shared:shared-components-parent::1 for project:
> null:file-management:jar:1.0 from the repository.
> [DEBUG] org.apache.maven.shared:file-management:jar:1.0:runtime (selected
> for runtime)
> [DEBUG] org.codehaus.plexus:plexus-utils:jar:1.0.4:runtime (selected for
> runtime)
> [DEBUG] Configuring mojo
> 'org.apache.maven.plugins:maven-clean-plugin:2.1:clean' -->
> [DEBUG] (f) directory =
> /Users/vmassol/dev/maven/trunks/core-integration-testing/core-integration-tests/src/test/resources/it0115-customArtifactHandlerAndCustomLifecycle/test-project/target
> [DEBUG] (f) outputDirectory =
> /Users/vmassol/dev/maven/trunks/core-integration-testing/core-integration-tests/src/test/resources/it0115-customArtifactHandlerAndCustomLifecycle/test-project/target/classes
> [DEBUG] (f) testOutputDirectory =
> /Users/vmassol/dev/maven/trunks/core-integration-testing/core-integration-tests/src/test/resources/it0115-customArtifactHandlerAndCustomLifec
