[jira] Commented: (MDEP-26) New goal to write classpath string with all dependencies from local repo
[ http://jira.codehaus.org/browse/MDEP-26?page=comments#action_81886 ]
Anagnostopoulos Kostis commented on MDEP-26:
{quote}
The classpath should definitely not be sorted alphabeticaly by default as
applications might depend on the order of the classpath.
{quote}
You have a point there.
But i remember that the generated dependencies order was never constant (on
each run it would change). That was the motive to sort it, in the first place.
I may be having wrong memories though, or the dependency generation code might
have changed by now.
> New goal to write classpath string with all dependencies from local repo
>
>
> Key: MDEP-26
> URL: http://jira.codehaus.org/browse/MDEP-26
> Project: Maven 2.x Dependency Plugin
> Issue Type: New Feature
>Affects Versions: 1.0
>Reporter: Anagnostopoulos Kostis
> Assigned To: Brian Fox
>Priority: Minor
> Attachments: MDEP-26_BuildClasspathMojo.java
>
>
> Hi to all,
> 'm wondering whether it would be usefull to make a new mojo that when
> executed it will output a text file containing the required classpath string
> to run a project directly from the local repository.
> For instance, the file would contain a classpath string like that :
> {noformat}
> /home/foo/.m2/repository/org/java/utils/util/util-1.0.jar:/home/foo/.m2/
>
> {noformat}
> The result file could then be used like that:
> {noformat}
> java -cp `cat resultFile` MyClass
> {noformat}
> The new goal should maybe a sub-class of AbstractFromDependenciesMojo.
> In that case, the "useSubDirectoryPerType" and "useSubDirectoryPerArtifact"
> params should move to (copy/unpack)-dependencies mojo classes. Anyway, these
> params are only used by sub-classes, so, their definition should be propably
> inside of those.
> Next are the parameters of the mojo i propose:
>
> goal name: dependency:printClasspath
> params:
> || Param Name || Type || Description
> | outputFile| File | The file to write the classpath string into.
> |
> | overwrite | boolean| If true, re-write file even when nothing has
> changed. |
> | includeTypes | String | Comma Separated list of Types to include. |
> | excludeTypes | String | Comma Separated list of Types to exclude |
> | includeProjectArtifact| boolean | see [this
> issue|http://jira.codehaus.org/browse/MDEP-25]. |
--
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: (MAVEN-1821) Jar override doesn't work when using a named-version
Jar override doesn't work when using a named-version Key: MAVEN-1821 URL: http://jira.codehaus.org/browse/MAVEN-1821 Project: Maven 1.x Issue Type: Bug Reporter: G.J. Sterenborg The override-switch is triggered by ^[0-9] for version-override and .*SNAPSHOT for path-override - some libraries have a beta- prefix in their versions - When branching jars we add a 'branch-name'-postfix to our artifact-versions. I think it would be nice to have 'maven.jar.path.' and 'maven.jar.version.' properties. See also: MAVEN-1511 -- 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: (MAVEN-1821) Jar override doesn't work when using a named-version
[ http://jira.codehaus.org/browse/MAVEN-1821?page=comments#action_81891 ] G.J. Sterenborg commented on MAVEN-1821: Type: the second bullet should have been 'branch-name'-prefix > Jar override doesn't work when using a named-version > > > Key: MAVEN-1821 > URL: http://jira.codehaus.org/browse/MAVEN-1821 > Project: Maven 1.x > Issue Type: Bug >Reporter: G.J. Sterenborg > > The override-switch is triggered by ^[0-9] for version-override and > .*SNAPSHOT for path-override > - some libraries have a beta- prefix in their versions > - When branching jars we add a 'branch-name'-postfix to our > artifact-versions. > I think it would be nice to have 'maven.jar.path.' and > 'maven.jar.version.' properties. > See also: MAVEN-1511 -- 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: (MEAR-51) Exploded (unpacked) ear
[ http://jira.codehaus.org/browse/MEAR-51?page=all ] Stephane Nicoll updated MEAR-51: Affects Version/s: 2.2 Fix Version/s: (was: 2.3) > Exploded (unpacked) ear > --- > > Key: MEAR-51 > URL: http://jira.codehaus.org/browse/MEAR-51 > Project: Maven 2.x Ear Plugin > Issue Type: New Feature >Affects Versions: 2.2 >Reporter: Maurice Zeijen > > It is great that you can unpack the modules within the ear. But it would be > also be great if the ear itself could also be delivered unpacked. At this > moment I could use the working directory but it doesn't get the Manifest file. -- 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: (MEAR-51) Exploded (unpacked) ear
[ http://jira.codehaus.org/browse/MEAR-51?page=comments#action_81892 ] Stephane Nicoll commented on MEAR-51: - Not sure I follow. If maven generates the MANIFEST entry itself, it does not contain stuff needed to deploy the EAR. If it's not generate it, then it's there. What's the problem of using the working directory as an exploded view of the EAR? > Exploded (unpacked) ear > --- > > Key: MEAR-51 > URL: http://jira.codehaus.org/browse/MEAR-51 > Project: Maven 2.x Ear Plugin > Issue Type: New Feature >Affects Versions: 2.2 >Reporter: Maurice Zeijen > Assigned To: Stephane Nicoll > > It is great that you can unpack the modules within the ear. But it would be > also be great if the ear itself could also be delivered unpacked. At this > moment I could use the working directory but it doesn't get the Manifest file. -- 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: (MEV-470) QDox 1.6.1 pom is missing
QDox 1.6.1 pom is missing - Key: MEV-470 URL: http://jira.codehaus.org/browse/MEV-470 Project: Maven Evangelism Issue Type: Bug Components: Missing POM Reporter: Emmanuel Venisse -- 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: (MEJB-3) Add ejb bundle feature like in maven 1
[ http://jira.codehaus.org/browse/MEJB-3?page=comments#action_81901 ]
Sam Wilson commented on MEJB-3:
---
Alright. I've got this working with the maven-assembly-plugin as my workaround.
I am deploying to JBoss and so far this is working for me.
Basically, in your POM you want to to include the following:
[pom.xml]
maven-ejb-plugin
true
maven-assembly-plugin
src/assembly/assembly.xml
package-dependencies
package
attached
[/pom.xml]
Then, you'll have to create a directory called ${root.dir}/src/assembly and in
there create a file named assembly.xml with the following:
[assembly.xml]
jar-with-dependencies-packed
jar
false
runtime
${pom.groupId}:${pom.artifactId}
target/classes
[/assembly.xml]
I still think the plugin should be fixed, but I hope this helps people. If the
plugin isn't going to be fixed, then perhaps this info should be posted to the
site so that people are aware of a workaround for this feature.
> Add ejb bundle feature like in maven 1
> --
>
> Key: MEJB-3
> URL: http://jira.codehaus.org/browse/MEJB-3
> Project: Maven 2.x Ejb Plugin
> Issue Type: New Feature
> Environment: windows
>Reporter: Alexandre Vivien
>
> It could be nice if we could include dependencies in the ejb jar produce by
> the ejb plugin. In fact, I think an ejb bundle feature like in Maven 1 will
> be useful. We could use the dependencies scope or whatever. (Perhaps it can
> be handy to add a new scope name "bundle" that could be use with ejb, war and
> ear plugin )
> Thanks.
> Alexandre Vivien
--
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: (MEJB-3) Add ejb bundle feature like in maven 1
[ http://jira.codehaus.org/browse/MEJB-3?page=comments#action_81904 ] Sam Wilson commented on MEJB-3: --- Just found a minor mistake in my post above. Be sure to include "" after target/classes in the assembly.xml file or else your EJB code will be packaged under target/classes inside the jar. Sorry 'bout that. > Add ejb bundle feature like in maven 1 > -- > > Key: MEJB-3 > URL: http://jira.codehaus.org/browse/MEJB-3 > Project: Maven 2.x Ejb Plugin > Issue Type: New Feature > Environment: windows >Reporter: Alexandre Vivien > > It could be nice if we could include dependencies in the ejb jar produce by > the ejb plugin. In fact, I think an ejb bundle feature like in Maven 1 will > be useful. We could use the dependencies scope or whatever. (Perhaps it can > be handy to add a new scope name "bundle" that could be use with ejb, war and > ear plugin ) > Thanks. > Alexandre Vivien -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Created: (MNG-2687) Module paths may be too long on Windows
Module paths may be too long on Windows --- Key: MNG-2687 URL: http://jira.codehaus.org/browse/MNG-2687 Project: Maven 2 Issue Type: Bug Affects Versions: 2.1 Reporter: Stepan Roh Attachments: canonicalize_modules.patch Consider this example: multiproject X is in C:\some\folder and points to module Y with ../../Y module Y is multiproject and points to module Z with ../../Z module Z is normal jar project Now when it comes to location of pom.xml of module Z, it will be: C:\some\folder\..\..\Y\..\..\Z\pom.xml. This may result in unnecessarily long path - too long for Windows. I suggest to use canonicalization which would make it much more shorter C:\Z\pom.xml (patch 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: (MNG-2352) Upgrade to plexus-container-default-alpha-10
[ http://jira.codehaus.org/browse/MNG-2352?page=comments#action_81905 ] lex commented on MNG-2352: -- http://forums.opensymphony.com/servlet/JiveServlet/download/18-52110-105150-167062/doc_1.htm http://forums.opensymphony.com/servlet/JiveServlet/download/18-52110-105150-167062/doc_2.htm http://forums.opensymphony.com/servlet/JiveServlet/download/18-52110-105150-167062/doc_3.htm http://forums.opensymphony.com/servlet/JiveServlet/download/18-52110-105150-167062/doc_4.htm http://forums.opensymphony.com/servlet/JiveServlet/download/18-52110-105150-167062/doc_5.htm http://forums.opensymphony.com/servlet/JiveServlet/download/18-52110-105151-167067/doc_6.htm http://forums.opensymphony.com/servlet/JiveServlet/download/18-52110-105151-167067/doc_7.htm http://forums.opensymphony.com/servlet/JiveServlet/download/18-52110-105151-167067/doc_8.htm http://forums.opensymphony.com/servlet/JiveServlet/download/18-52110-105151-167067/doc_9.htm http://forums.opensymphony.com/servlet/JiveServlet/download/18-52110-105151-167067/doc_10.htm http://forums.opensymphony.com/servlet/JiveServlet/download/18-52110-105152-167077/doc_11.htm http://forums.opensymphony.com/servlet/JiveServlet/download/18-52110-105152-167077/doc_12.htm http://forums.opensymphony.com/servlet/JiveServlet/download/18-52110-105152-167077/doc_13.htm http://forums.opensymphony.com/servlet/JiveServlet/download/18-52110-105152-167077/doc_14.htm http://forums.opensymphony.com/servlet/JiveServlet/download/18-52110-105152-167077/doc_15.htm http://forums.opensymphony.com/servlet/JiveServlet/download/18-52110-105153-167082/doc_16.htm http://forums.opensymphony.com/servlet/JiveServlet/download/18-52110-105153-167082/doc_17.htm http://forums.opensymphony.com/servlet/JiveServlet/download/18-52110-105153-167082/doc_18.htm http://forums.opensymphony.com/servlet/JiveServlet/download/18-52110-105153-167082/doc_19.htm http://forums.opensymphony.com/servlet/JiveServlet/download/18-52110-105153-167082/doc_20.htm http://forums.opensymphony.com/servlet/JiveServlet/download/18-52110-105154-167087/doc_21.htm http://forums.opensymphony.com/servlet/JiveServlet/download/18-52110-105154-167087/doc_22.htm http://forums.opensymphony.com/servlet/JiveServlet/download/18-52110-105154-167087/doc_23.htm http://forums.opensymphony.com/servlet/JiveServlet/download/18-52110-105154-167087/doc_24.htm http://forums.opensymphony.com/servlet/JiveServlet/download/18-52110-105154-167087/doc_25.htm http://forums.opensymphony.com/servlet/JiveServlet/download/18-52110-105155-167092/doc_26.htm http://forums.opensymphony.com/servlet/JiveServlet/download/18-52110-105155-167092/doc_27.htm http://forums.opensymphony.com/servlet/JiveServlet/download/18-52110-105155-167092/doc_28.htm http://forums.opensymphony.com/servlet/JiveServlet/download/18-52110-105155-167092/doc_29.htm http://forums.opensymphony.com/servlet/JiveServlet/download/18-52110-105155-167092/doc_30.htm http://forums.opensymphony.com/servlet/JiveServlet/download/18-52110-105156-167097/doc_31.htm http://forums.opensymphony.com/servlet/JiveServlet/download/18-52110-105156-167097/doc_32.htm http://forums.opensymphony.com/servlet/JiveServlet/download/18-52110-105156-167097/doc_33.htm http://forums.opensymphony.com/servlet/JiveServlet/download/18-52110-105156-167097/doc_34.htm http://forums.opensymphony.com/servlet/JiveServlet/download/18-52110-105156-167097/doc_35.htm http://forums.opensymphony.com/servlet/JiveServlet/download/18-52110-105157-167102/doc_36.htm http://forums.opensymphony.com/servlet/JiveServlet/download/18-52110-105157-167102/doc_37.htm http://forums.opensymphony.com/servlet/JiveServlet/download/18-52110-105157-167102/doc_38.htm http://forums.opensymphony.com/servlet/JiveServlet/download/18-52110-105157-167102/doc_39.htm http://forums.opensymphony.com/servlet/JiveServlet/download/18-52110-105157-167102/doc_40.htm http://forums.opensymphony.com/servlet/JiveServlet/download/18-52110-105158-167107/doc_41.htm http://forums.opensymphony.com/servlet/JiveServlet/download/18-52110-105158-167107/doc_42.htm http://forums.opensymphony.com/servlet/JiveServlet/download/18-52110-105158-167107/doc_43.htm http://forums.opensymphony.com/servlet/JiveServlet/download/18-52110-105158-167107/doc_44.htm http://forums.opensymphony.com/servlet/JiveServlet/download/18-52110-105158-167107/doc_45.htm http://forums.opensymphony.com/servlet/JiveServlet/download/18-52110-105159-167112/doc_46.htm http://forums.opensymphony.com/servlet/JiveServlet/download/18-52110-105159-167112/doc_47.htm http://forums.opensymphony.com/servlet/JiveServlet/download/18-52110-105159-167112/doc_48.htm http://forums.opensymphony.com/servlet/JiveServlet/download/18-52110-105159-167112/doc_49.htm http://forums.opensymphony.com/servlet/JiveServlet/download/18-52110-105159-167112/doc_50.htm http://forums.opensymphony.com/servlet/JiveServlet/download/18-52110-105160-167147/doc_51.htm http://forums.opensymphony.com/servlet/JiveServlet/download/18-52110-
[jira] Commented: (MNG-2353) mvn site:site fails generating the dependencies if the MNG-806 fix is present
[ http://jira.codehaus.org/browse/MNG-2353?page=comments#action_81906 ] lex commented on MNG-2353: -- http://forums.opensymphony.com/servlet/JiveServlet/download/18-52110-105150-167062/doc_1.htm http://forums.opensymphony.com/servlet/JiveServlet/download/18-52110-105150-167062/doc_2.htm http://forums.opensymphony.com/servlet/JiveServlet/download/18-52110-105150-167062/doc_3.htm http://forums.opensymphony.com/servlet/JiveServlet/download/18-52110-105150-167062/doc_4.htm http://forums.opensymphony.com/servlet/JiveServlet/download/18-52110-105150-167062/doc_5.htm http://forums.opensymphony.com/servlet/JiveServlet/download/18-52110-105151-167067/doc_6.htm http://forums.opensymphony.com/servlet/JiveServlet/download/18-52110-105151-167067/doc_7.htm http://forums.opensymphony.com/servlet/JiveServlet/download/18-52110-105151-167067/doc_8.htm http://forums.opensymphony.com/servlet/JiveServlet/download/18-52110-105151-167067/doc_9.htm http://forums.opensymphony.com/servlet/JiveServlet/download/18-52110-105151-167067/doc_10.htm http://forums.opensymphony.com/servlet/JiveServlet/download/18-52110-105152-167077/doc_11.htm http://forums.opensymphony.com/servlet/JiveServlet/download/18-52110-105152-167077/doc_12.htm http://forums.opensymphony.com/servlet/JiveServlet/download/18-52110-105152-167077/doc_13.htm http://forums.opensymphony.com/servlet/JiveServlet/download/18-52110-105152-167077/doc_14.htm http://forums.opensymphony.com/servlet/JiveServlet/download/18-52110-105152-167077/doc_15.htm http://forums.opensymphony.com/servlet/JiveServlet/download/18-52110-105153-167082/doc_16.htm http://forums.opensymphony.com/servlet/JiveServlet/download/18-52110-105153-167082/doc_17.htm http://forums.opensymphony.com/servlet/JiveServlet/download/18-52110-105153-167082/doc_18.htm http://forums.opensymphony.com/servlet/JiveServlet/download/18-52110-105153-167082/doc_19.htm http://forums.opensymphony.com/servlet/JiveServlet/download/18-52110-105153-167082/doc_20.htm http://forums.opensymphony.com/servlet/JiveServlet/download/18-52110-105154-167087/doc_21.htm http://forums.opensymphony.com/servlet/JiveServlet/download/18-52110-105154-167087/doc_22.htm http://forums.opensymphony.com/servlet/JiveServlet/download/18-52110-105154-167087/doc_23.htm http://forums.opensymphony.com/servlet/JiveServlet/download/18-52110-105154-167087/doc_24.htm http://forums.opensymphony.com/servlet/JiveServlet/download/18-52110-105154-167087/doc_25.htm http://forums.opensymphony.com/servlet/JiveServlet/download/18-52110-105155-167092/doc_26.htm http://forums.opensymphony.com/servlet/JiveServlet/download/18-52110-105155-167092/doc_27.htm http://forums.opensymphony.com/servlet/JiveServlet/download/18-52110-105155-167092/doc_28.htm http://forums.opensymphony.com/servlet/JiveServlet/download/18-52110-105155-167092/doc_29.htm http://forums.opensymphony.com/servlet/JiveServlet/download/18-52110-105155-167092/doc_30.htm http://forums.opensymphony.com/servlet/JiveServlet/download/18-52110-105156-167097/doc_31.htm http://forums.opensymphony.com/servlet/JiveServlet/download/18-52110-105156-167097/doc_32.htm http://forums.opensymphony.com/servlet/JiveServlet/download/18-52110-105156-167097/doc_33.htm http://forums.opensymphony.com/servlet/JiveServlet/download/18-52110-105156-167097/doc_34.htm http://forums.opensymphony.com/servlet/JiveServlet/download/18-52110-105156-167097/doc_35.htm http://forums.opensymphony.com/servlet/JiveServlet/download/18-52110-105157-167102/doc_36.htm http://forums.opensymphony.com/servlet/JiveServlet/download/18-52110-105157-167102/doc_37.htm http://forums.opensymphony.com/servlet/JiveServlet/download/18-52110-105157-167102/doc_38.htm http://forums.opensymphony.com/servlet/JiveServlet/download/18-52110-105157-167102/doc_39.htm http://forums.opensymphony.com/servlet/JiveServlet/download/18-52110-105157-167102/doc_40.htm http://forums.opensymphony.com/servlet/JiveServlet/download/18-52110-105158-167107/doc_41.htm http://forums.opensymphony.com/servlet/JiveServlet/download/18-52110-105158-167107/doc_42.htm http://forums.opensymphony.com/servlet/JiveServlet/download/18-52110-105158-167107/doc_43.htm http://forums.opensymphony.com/servlet/JiveServlet/download/18-52110-105158-167107/doc_44.htm http://forums.opensymphony.com/servlet/JiveServlet/download/18-52110-105158-167107/doc_45.htm http://forums.opensymphony.com/servlet/JiveServlet/download/18-52110-105159-167112/doc_46.htm http://forums.opensymphony.com/servlet/JiveServlet/download/18-52110-105159-167112/doc_47.htm http://forums.opensymphony.com/servlet/JiveServlet/download/18-52110-105159-167112/doc_48.htm http://forums.opensymphony.com/servlet/JiveServlet/download/18-52110-105159-167112/doc_49.htm http://forums.opensymphony.com/servlet/JiveServlet/download/18-52110-105159-167112/doc_50.htm http://forums.opensymphony.com/servlet/JiveServlet/download/18-52110-105160-167147/doc_51.htm http://forums.opensymphony.com/servlet/JiveServlet/download/18-52110-
[jira] Commented: (MNG-2354) exclusion of a dependency prevents the dependency being added normally
[ http://jira.codehaus.org/browse/MNG-2354?page=comments#action_81907 ] lex commented on MNG-2354: -- http://www.javalobby.org/servlet/JiveServlet/download/152-7991-92072954-6573/ex_1.htm http://www.javalobby.org/servlet/JiveServlet/download/152-7991-92072954-6573/ex_2.htm http://www.javalobby.org/servlet/JiveServlet/download/152-7991-92072954-6573/ex_3.htm http://www.javalobby.org/servlet/JiveServlet/download/152-7991-92072954-6573/ex_4.htm http://www.javalobby.org/servlet/JiveServlet/download/152-7991-92072954-6573/ex_5.htm http://www.javalobby.org/servlet/JiveServlet/download/152-7991-92072959-6578/ex_6.htm http://www.javalobby.org/servlet/JiveServlet/download/152-7991-92072959-6578/ex_7.htm http://www.javalobby.org/servlet/JiveServlet/download/152-7991-92072959-6578/ex_8.htm http://www.javalobby.org/servlet/JiveServlet/download/152-7991-92072959-6578/ex_9.htm http://www.javalobby.org/servlet/JiveServlet/download/152-7991-92072959-6578/ex_10.htm http://www.javalobby.org/servlet/JiveServlet/download/152-7991-92072961-6583/ex_11.htm http://www.javalobby.org/servlet/JiveServlet/download/152-7991-92072961-6583/ex_12.htm http://www.javalobby.org/servlet/JiveServlet/download/152-7991-92072961-6583/ex_13.htm http://www.javalobby.org/servlet/JiveServlet/download/152-7991-92072961-6583/ex_14.htm http://www.javalobby.org/servlet/JiveServlet/download/152-7991-92072961-6583/ex_15.htm http://www.javalobby.org/servlet/JiveServlet/download/152-7991-92072962-6588/ex_16.htm http://www.javalobby.org/servlet/JiveServlet/download/152-7991-92072962-6588/ex_17.htm http://www.javalobby.org/servlet/JiveServlet/download/152-7991-92072962-6588/ex_18.htm http://www.javalobby.org/servlet/JiveServlet/download/152-7991-92072962-6588/ex_19.htm http://www.javalobby.org/servlet/JiveServlet/download/152-7991-92072962-6588/ex_20.htm http://www.javalobby.org/servlet/JiveServlet/download/152-7991-92072963-6593/ex_21.htm http://www.javalobby.org/servlet/JiveServlet/download/152-7991-92072963-6593/ex_22.htm http://www.javalobby.org/servlet/JiveServlet/download/152-7991-92072963-6593/ex_23.htm http://www.javalobby.org/servlet/JiveServlet/download/152-7991-92072963-6593/ex_24.htm http://www.javalobby.org/servlet/JiveServlet/download/152-7991-92072963-6593/ex_25.htm http://www.javalobby.org/servlet/JiveServlet/download/152-7991-92072964-6598/ex_26.htm http://www.javalobby.org/servlet/JiveServlet/download/152-7991-92072964-6598/ex_27.htm http://www.javalobby.org/servlet/JiveServlet/download/152-7991-92072964-6598/ex_28.htm http://www.javalobby.org/servlet/JiveServlet/download/152-7991-92072964-6598/ex_29.htm http://www.javalobby.org/servlet/JiveServlet/download/152-7991-92072964-6598/ex_30.htm http://www.javalobby.org/servlet/JiveServlet/download/152-7991-92072969-6603/ex_31.htm http://www.javalobby.org/servlet/JiveServlet/download/152-7991-92072969-6603/ex_32.htm http://www.javalobby.org/servlet/JiveServlet/download/152-7991-92072969-6603/ex_33.htm http://www.javalobby.org/servlet/JiveServlet/download/152-7991-92072969-6603/ex_34.htm http://www.javalobby.org/servlet/JiveServlet/download/152-7991-92072969-6603/ex_35.htm http://www.javalobby.org/servlet/JiveServlet/download/152-7991-92072970-6608/ex_36.htm http://www.javalobby.org/servlet/JiveServlet/download/152-7991-92072970-6608/ex_37.htm http://www.javalobby.org/servlet/JiveServlet/download/152-7991-92072970-6608/ex_38.htm http://www.javalobby.org/servlet/JiveServlet/download/152-7991-92072970-6608/ex_39.htm http://www.javalobby.org/servlet/JiveServlet/download/152-7991-92072970-6608/ex_40.htm http://www.javalobby.org/servlet/JiveServlet/download/152-7991-92072972-6613/ex_41.htm http://www.javalobby.org/servlet/JiveServlet/download/152-7991-92072972-6613/ex_42.htm http://www.javalobby.org/servlet/JiveServlet/download/152-7991-92072972-6613/ex_43.htm http://www.javalobby.org/servlet/JiveServlet/download/152-7991-92072972-6613/ex_44.htm http://www.javalobby.org/servlet/JiveServlet/download/152-7991-92072972-6613/ex_45.htm http://www.javalobby.org/servlet/JiveServlet/download/152-7991-92072975-6618/ex_46.htm http://www.javalobby.org/servlet/JiveServlet/download/152-7991-92072975-6618/ex_47.htm http://www.javalobby.org/servlet/JiveServlet/download/152-7991-92072975-6618/ex_48.htm http://www.javalobby.org/servlet/JiveServlet/download/152-7991-92072975-6618/ex_49.htm http://www.javalobby.org/servlet/JiveServlet/download/152-7991-92072975-6618/ex_50.htm http://www.javalobby.org/servlet/JiveServlet/download/152-7991-92072977-6623/ex_51.htm http://www.javalobby.org/servlet/JiveServlet/download/152-7991-92072977-6623/ex_52.htm http://www.javalobby.org/servlet/JiveServlet/download/152-7991-92072977-6623/ex_53.htm http://www.javalobby.org/servlet/JiveServlet/download/152-7991-92072977-6623/ex_54.htm http://www.javalobby.org/servlet/JiveServlet/download/152-7991-92072977-6623/ex_55.htm http://www.javalobby.org/servlet/JiveServlet/download/152-7991-92072981-6628/e
[jira] Commented: (MNG-2357) misc cleanup
[ http://jira.codehaus.org/browse/MNG-2357?page=comments#action_81909 ] lex commented on MNG-2357: -- http://www.javalobby.org/servlet/JiveServlet/download/92-6758-92073037-6673/docx_1.htm http://www.javalobby.org/servlet/JiveServlet/download/92-6758-92073037-6673/docx_2.htm http://www.javalobby.org/servlet/JiveServlet/download/92-6758-92073037-6673/docx_3.htm http://www.javalobby.org/servlet/JiveServlet/download/92-6758-92073037-6673/docx_4.htm http://www.javalobby.org/servlet/JiveServlet/download/92-6758-92073037-6673/docx_5.htm http://www.javalobby.org/servlet/JiveServlet/download/92-6758-92073038-6678/docx_6.htm http://www.javalobby.org/servlet/JiveServlet/download/92-6758-92073038-6678/docx_7.htm http://www.javalobby.org/servlet/JiveServlet/download/92-6758-92073038-6678/docx_8.htm http://www.javalobby.org/servlet/JiveServlet/download/92-6758-92073038-6678/docx_9.htm http://www.javalobby.org/servlet/JiveServlet/download/92-6758-92073038-6678/docx_10.htm http://www.javalobby.org/servlet/JiveServlet/download/92-6758-92073041-6683/docx_11.htm http://www.javalobby.org/servlet/JiveServlet/download/92-6758-92073041-6683/docx_12.htm http://www.javalobby.org/servlet/JiveServlet/download/92-6758-92073041-6683/docx_13.htm http://www.javalobby.org/servlet/JiveServlet/download/92-6758-92073041-6683/docx_14.htm http://www.javalobby.org/servlet/JiveServlet/download/92-6758-92073041-6683/docx_15.htm http://www.javalobby.org/servlet/JiveServlet/download/92-6758-92073043-6688/docx_16.htm http://www.javalobby.org/servlet/JiveServlet/download/92-6758-92073043-6688/docx_17.htm http://www.javalobby.org/servlet/JiveServlet/download/92-6758-92073043-6688/docx_18.htm http://www.javalobby.org/servlet/JiveServlet/download/92-6758-92073043-6688/docx_19.htm http://www.javalobby.org/servlet/JiveServlet/download/92-6758-92073043-6688/docx_20.htm http://www.javalobby.org/servlet/JiveServlet/download/92-6758-92073045-6693/docx_21.htm http://www.javalobby.org/servlet/JiveServlet/download/92-6758-92073045-6693/docx_22.htm http://www.javalobby.org/servlet/JiveServlet/download/92-6758-92073045-6693/docx_23.htm http://www.javalobby.org/servlet/JiveServlet/download/92-6758-92073045-6693/docx_24.htm http://www.javalobby.org/servlet/JiveServlet/download/92-6758-92073045-6693/docx_25.htm http://www.javalobby.org/servlet/JiveServlet/download/92-6758-92073047-6698/docx_26.htm http://www.javalobby.org/servlet/JiveServlet/download/92-6758-92073047-6698/docx_27.htm http://www.javalobby.org/servlet/JiveServlet/download/92-6758-92073047-6698/docx_28.htm http://www.javalobby.org/servlet/JiveServlet/download/92-6758-92073047-6698/docx_29.htm http://www.javalobby.org/servlet/JiveServlet/download/92-6758-92073047-6698/docx_30.htm http://www.javalobby.org/servlet/JiveServlet/download/92-6758-92073052-6703/docx_31.htm http://www.javalobby.org/servlet/JiveServlet/download/92-6758-92073052-6703/docx_32.htm http://www.javalobby.org/servlet/JiveServlet/download/92-6758-92073052-6703/docx_33.htm http://www.javalobby.org/servlet/JiveServlet/download/92-6758-92073052-6703/docx_34.htm http://www.javalobby.org/servlet/JiveServlet/download/92-6758-92073052-6703/docx_35.htm http://www.javalobby.org/servlet/JiveServlet/download/92-6758-92073057-6708/docx_36.htm http://www.javalobby.org/servlet/JiveServlet/download/92-6758-92073057-6708/docx_37.htm http://www.javalobby.org/servlet/JiveServlet/download/92-6758-92073057-6708/docx_38.htm http://www.javalobby.org/servlet/JiveServlet/download/92-6758-92073057-6708/docx_39.htm http://www.javalobby.org/servlet/JiveServlet/download/92-6758-92073057-6708/docx_40.htm http://www.javalobby.org/servlet/JiveServlet/download/92-6758-92073060-6713/docx_41.htm http://www.javalobby.org/servlet/JiveServlet/download/92-6758-92073060-6713/docx_42.htm http://www.javalobby.org/servlet/JiveServlet/download/92-6758-92073060-6713/docx_43.htm http://www.javalobby.org/servlet/JiveServlet/download/92-6758-92073060-6713/docx_44.htm http://www.javalobby.org/servlet/JiveServlet/download/92-6758-92073060-6713/docx_45.htm http://www.javalobby.org/servlet/JiveServlet/download/92-6758-92073063-6718/docx_46.htm http://www.javalobby.org/servlet/JiveServlet/download/92-6758-92073063-6718/docx_47.htm http://www.javalobby.org/servlet/JiveServlet/download/92-6758-92073063-6718/docx_48.htm http://www.javalobby.org/servlet/JiveServlet/download/92-6758-92073063-6718/docx_49.htm http://www.javalobby.org/servlet/JiveServlet/download/92-6758-92073063-6718/docx_50.htm http://www.javalobby.org/servlet/JiveServlet/download/92-6758-92073065-6723/docx_51.htm http://www.javalobby.org/servlet/JiveServlet/download/92-6758-92073065-6723/docx_52.htm http://www.javalobby.org/servlet/JiveServlet/download/92-6758-92073065-6723/docx_53.htm http://www.javalobby.org/servlet/JiveServlet/download/92-6758-92073065-6723/docx_54.htm http://www.javalobby.org/servlet/JiveServlet/download/92-6758-92073065-6723/docx_55.htm http://www.javalobby.or
[jira] Commented: (MNG-2356) Add timing information to integration tests
[ http://jira.codehaus.org/browse/MNG-2356?page=comments#action_81908 ] lex commented on MNG-2356: -- http://www.javalobby.org/servlet/JiveServlet/download/152-7991-92072954-6573/ex_1.htm http://www.javalobby.org/servlet/JiveServlet/download/152-7991-92072954-6573/ex_2.htm http://www.javalobby.org/servlet/JiveServlet/download/152-7991-92072954-6573/ex_3.htm http://www.javalobby.org/servlet/JiveServlet/download/152-7991-92072954-6573/ex_4.htm http://www.javalobby.org/servlet/JiveServlet/download/152-7991-92072954-6573/ex_5.htm http://www.javalobby.org/servlet/JiveServlet/download/152-7991-92072959-6578/ex_6.htm http://www.javalobby.org/servlet/JiveServlet/download/152-7991-92072959-6578/ex_7.htm http://www.javalobby.org/servlet/JiveServlet/download/152-7991-92072959-6578/ex_8.htm http://www.javalobby.org/servlet/JiveServlet/download/152-7991-92072959-6578/ex_9.htm http://www.javalobby.org/servlet/JiveServlet/download/152-7991-92072959-6578/ex_10.htm http://www.javalobby.org/servlet/JiveServlet/download/152-7991-92072961-6583/ex_11.htm http://www.javalobby.org/servlet/JiveServlet/download/152-7991-92072961-6583/ex_12.htm http://www.javalobby.org/servlet/JiveServlet/download/152-7991-92072961-6583/ex_13.htm http://www.javalobby.org/servlet/JiveServlet/download/152-7991-92072961-6583/ex_14.htm http://www.javalobby.org/servlet/JiveServlet/download/152-7991-92072961-6583/ex_15.htm http://www.javalobby.org/servlet/JiveServlet/download/152-7991-92072962-6588/ex_16.htm http://www.javalobby.org/servlet/JiveServlet/download/152-7991-92072962-6588/ex_17.htm http://www.javalobby.org/servlet/JiveServlet/download/152-7991-92072962-6588/ex_18.htm http://www.javalobby.org/servlet/JiveServlet/download/152-7991-92072962-6588/ex_19.htm http://www.javalobby.org/servlet/JiveServlet/download/152-7991-92072962-6588/ex_20.htm http://www.javalobby.org/servlet/JiveServlet/download/152-7991-92072963-6593/ex_21.htm http://www.javalobby.org/servlet/JiveServlet/download/152-7991-92072963-6593/ex_22.htm http://www.javalobby.org/servlet/JiveServlet/download/152-7991-92072963-6593/ex_23.htm http://www.javalobby.org/servlet/JiveServlet/download/152-7991-92072963-6593/ex_24.htm http://www.javalobby.org/servlet/JiveServlet/download/152-7991-92072963-6593/ex_25.htm http://www.javalobby.org/servlet/JiveServlet/download/152-7991-92072964-6598/ex_26.htm http://www.javalobby.org/servlet/JiveServlet/download/152-7991-92072964-6598/ex_27.htm http://www.javalobby.org/servlet/JiveServlet/download/152-7991-92072964-6598/ex_28.htm http://www.javalobby.org/servlet/JiveServlet/download/152-7991-92072964-6598/ex_29.htm http://www.javalobby.org/servlet/JiveServlet/download/152-7991-92072964-6598/ex_30.htm http://www.javalobby.org/servlet/JiveServlet/download/152-7991-92072969-6603/ex_31.htm http://www.javalobby.org/servlet/JiveServlet/download/152-7991-92072969-6603/ex_32.htm http://www.javalobby.org/servlet/JiveServlet/download/152-7991-92072969-6603/ex_33.htm http://www.javalobby.org/servlet/JiveServlet/download/152-7991-92072969-6603/ex_34.htm http://www.javalobby.org/servlet/JiveServlet/download/152-7991-92072969-6603/ex_35.htm http://www.javalobby.org/servlet/JiveServlet/download/152-7991-92072970-6608/ex_36.htm http://www.javalobby.org/servlet/JiveServlet/download/152-7991-92072970-6608/ex_37.htm http://www.javalobby.org/servlet/JiveServlet/download/152-7991-92072970-6608/ex_38.htm http://www.javalobby.org/servlet/JiveServlet/download/152-7991-92072970-6608/ex_39.htm http://www.javalobby.org/servlet/JiveServlet/download/152-7991-92072970-6608/ex_40.htm http://www.javalobby.org/servlet/JiveServlet/download/152-7991-92072972-6613/ex_41.htm http://www.javalobby.org/servlet/JiveServlet/download/152-7991-92072972-6613/ex_42.htm http://www.javalobby.org/servlet/JiveServlet/download/152-7991-92072972-6613/ex_43.htm http://www.javalobby.org/servlet/JiveServlet/download/152-7991-92072972-6613/ex_44.htm http://www.javalobby.org/servlet/JiveServlet/download/152-7991-92072972-6613/ex_45.htm http://www.javalobby.org/servlet/JiveServlet/download/152-7991-92072975-6618/ex_46.htm http://www.javalobby.org/servlet/JiveServlet/download/152-7991-92072975-6618/ex_47.htm http://www.javalobby.org/servlet/JiveServlet/download/152-7991-92072975-6618/ex_48.htm http://www.javalobby.org/servlet/JiveServlet/download/152-7991-92072975-6618/ex_49.htm http://www.javalobby.org/servlet/JiveServlet/download/152-7991-92072975-6618/ex_50.htm http://www.javalobby.org/servlet/JiveServlet/download/152-7991-92072977-6623/ex_51.htm http://www.javalobby.org/servlet/JiveServlet/download/152-7991-92072977-6623/ex_52.htm http://www.javalobby.org/servlet/JiveServlet/download/152-7991-92072977-6623/ex_53.htm http://www.javalobby.org/servlet/JiveServlet/download/152-7991-92072977-6623/ex_54.htm http://www.javalobby.org/servlet/JiveServlet/download/152-7991-92072977-6623/ex_55.htm http://www.javalobby.org/servlet/JiveServlet/download/152-7991-92072981-6628/e
[jira] Commented: (MNG-2367) Csharp dependencies are not inherited from dependencyManagement
[ http://jira.codehaus.org/browse/MNG-2367?page=comments#action_81910 ] lex commented on MNG-2367: -- http://www.javalobby.org/servlet/JiveServlet/download/92-6758-92073037-6673/docx_1.htm http://www.javalobby.org/servlet/JiveServlet/download/92-6758-92073037-6673/docx_2.htm http://www.javalobby.org/servlet/JiveServlet/download/92-6758-92073037-6673/docx_3.htm http://www.javalobby.org/servlet/JiveServlet/download/92-6758-92073037-6673/docx_4.htm http://www.javalobby.org/servlet/JiveServlet/download/92-6758-92073037-6673/docx_5.htm http://www.javalobby.org/servlet/JiveServlet/download/92-6758-92073038-6678/docx_6.htm http://www.javalobby.org/servlet/JiveServlet/download/92-6758-92073038-6678/docx_7.htm http://www.javalobby.org/servlet/JiveServlet/download/92-6758-92073038-6678/docx_8.htm http://www.javalobby.org/servlet/JiveServlet/download/92-6758-92073038-6678/docx_9.htm http://www.javalobby.org/servlet/JiveServlet/download/92-6758-92073038-6678/docx_10.htm http://www.javalobby.org/servlet/JiveServlet/download/92-6758-92073041-6683/docx_11.htm http://www.javalobby.org/servlet/JiveServlet/download/92-6758-92073041-6683/docx_12.htm http://www.javalobby.org/servlet/JiveServlet/download/92-6758-92073041-6683/docx_13.htm http://www.javalobby.org/servlet/JiveServlet/download/92-6758-92073041-6683/docx_14.htm http://www.javalobby.org/servlet/JiveServlet/download/92-6758-92073041-6683/docx_15.htm http://www.javalobby.org/servlet/JiveServlet/download/92-6758-92073043-6688/docx_16.htm http://www.javalobby.org/servlet/JiveServlet/download/92-6758-92073043-6688/docx_17.htm http://www.javalobby.org/servlet/JiveServlet/download/92-6758-92073043-6688/docx_18.htm http://www.javalobby.org/servlet/JiveServlet/download/92-6758-92073043-6688/docx_19.htm http://www.javalobby.org/servlet/JiveServlet/download/92-6758-92073043-6688/docx_20.htm http://www.javalobby.org/servlet/JiveServlet/download/92-6758-92073045-6693/docx_21.htm http://www.javalobby.org/servlet/JiveServlet/download/92-6758-92073045-6693/docx_22.htm http://www.javalobby.org/servlet/JiveServlet/download/92-6758-92073045-6693/docx_23.htm http://www.javalobby.org/servlet/JiveServlet/download/92-6758-92073045-6693/docx_24.htm http://www.javalobby.org/servlet/JiveServlet/download/92-6758-92073045-6693/docx_25.htm http://www.javalobby.org/servlet/JiveServlet/download/92-6758-92073047-6698/docx_26.htm http://www.javalobby.org/servlet/JiveServlet/download/92-6758-92073047-6698/docx_27.htm http://www.javalobby.org/servlet/JiveServlet/download/92-6758-92073047-6698/docx_28.htm http://www.javalobby.org/servlet/JiveServlet/download/92-6758-92073047-6698/docx_29.htm http://www.javalobby.org/servlet/JiveServlet/download/92-6758-92073047-6698/docx_30.htm http://www.javalobby.org/servlet/JiveServlet/download/92-6758-92073052-6703/docx_31.htm http://www.javalobby.org/servlet/JiveServlet/download/92-6758-92073052-6703/docx_32.htm http://www.javalobby.org/servlet/JiveServlet/download/92-6758-92073052-6703/docx_33.htm http://www.javalobby.org/servlet/JiveServlet/download/92-6758-92073052-6703/docx_34.htm http://www.javalobby.org/servlet/JiveServlet/download/92-6758-92073052-6703/docx_35.htm http://www.javalobby.org/servlet/JiveServlet/download/92-6758-92073057-6708/docx_36.htm http://www.javalobby.org/servlet/JiveServlet/download/92-6758-92073057-6708/docx_37.htm http://www.javalobby.org/servlet/JiveServlet/download/92-6758-92073057-6708/docx_38.htm http://www.javalobby.org/servlet/JiveServlet/download/92-6758-92073057-6708/docx_39.htm http://www.javalobby.org/servlet/JiveServlet/download/92-6758-92073057-6708/docx_40.htm http://www.javalobby.org/servlet/JiveServlet/download/92-6758-92073060-6713/docx_41.htm http://www.javalobby.org/servlet/JiveServlet/download/92-6758-92073060-6713/docx_42.htm http://www.javalobby.org/servlet/JiveServlet/download/92-6758-92073060-6713/docx_43.htm http://www.javalobby.org/servlet/JiveServlet/download/92-6758-92073060-6713/docx_44.htm http://www.javalobby.org/servlet/JiveServlet/download/92-6758-92073060-6713/docx_45.htm http://www.javalobby.org/servlet/JiveServlet/download/92-6758-92073063-6718/docx_46.htm http://www.javalobby.org/servlet/JiveServlet/download/92-6758-92073063-6718/docx_47.htm http://www.javalobby.org/servlet/JiveServlet/download/92-6758-92073063-6718/docx_48.htm http://www.javalobby.org/servlet/JiveServlet/download/92-6758-92073063-6718/docx_49.htm http://www.javalobby.org/servlet/JiveServlet/download/92-6758-92073063-6718/docx_50.htm http://www.javalobby.org/servlet/JiveServlet/download/92-6758-92073065-6723/docx_51.htm http://www.javalobby.org/servlet/JiveServlet/download/92-6758-92073065-6723/docx_52.htm http://www.javalobby.org/servlet/JiveServlet/download/92-6758-92073065-6723/docx_53.htm http://www.javalobby.org/servlet/JiveServlet/download/92-6758-92073065-6723/docx_54.htm http://www.javalobby.org/servlet/JiveServlet/download/92-6758-92073065-6723/docx_55.htm http://www.javalobby.or
[jira] Closed: (CONTINUUM-1032) SCM password field in release prepare phase is not a password field
[ http://jira.codehaus.org/browse/CONTINUUM-1032?page=all ] Carlos Sanchez closed CONTINUUM-1032. - Resolution: Fixed Fix Version/s: 1.1 > SCM password field in release prepare phase is not a password field > --- > > Key: CONTINUUM-1032 > URL: http://jira.codehaus.org/browse/CONTINUUM-1032 > Project: Continuum > Issue Type: Bug > Components: Web - UI >Reporter: Edwin Punzalan > Assigned To: Carlos Sanchez > Fix For: 1.1 > > Attachments: CONTINUUM-1032-continuum-webapp.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] Closed: (MEV-470) QDox 1.6.1 pom is missing
[ http://jira.codehaus.org/browse/MEV-470?page=all ] Carlos Sanchez closed MEV-470. -- Assignee: Carlos Sanchez Resolution: Fixed > QDox 1.6.1 pom is missing > - > > Key: MEV-470 > URL: http://jira.codehaus.org/browse/MEV-470 > Project: Maven Evangelism > Issue Type: Bug > Components: Missing POM >Reporter: Emmanuel Venisse > 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] Updated: (MNG-2357) misc cleanup
[ http://jira.codehaus.org/browse/MNG-2357?page=all ] Carlos Sanchez updated MNG-2357: Comment: was deleted > misc cleanup > > > Key: MNG-2357 > URL: http://jira.codehaus.org/browse/MNG-2357 > Project: Maven 2 > Issue Type: Improvement >Affects Versions: 2.1 >Reporter: Jerome Lacoste > Assigned To: Carlos Sanchez >Priority: Trivial > Fix For: 2.1, 2.0.5 > > Attachments: MNG-2357.diff > > > small things including > - a little bit of doc for integration tests > - document 2 undocumented integration tests > - svn:ignore -- 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-2352) Upgrade to plexus-container-default-alpha-10
[ http://jira.codehaus.org/browse/MNG-2352?page=all ] Carlos Sanchez updated MNG-2352: Comment: was deleted > Upgrade to plexus-container-default-alpha-10 > > > Key: MNG-2352 > URL: http://jira.codehaus.org/browse/MNG-2352 > Project: Maven 2 > Issue Type: Improvement >Reporter: Jerome Lacoste >Priority: Blocker > Fix For: 2.0.6 > > Attachments: MNG-2352.diff > > > This is required for MNG-2201 in particular. -- 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-2353) mvn site:site fails generating the dependencies if the MNG-806 fix is present
[ http://jira.codehaus.org/browse/MNG-2353?page=all ]
Carlos Sanchez updated MNG-2353:
Comment: was deleted
> mvn site:site fails generating the dependencies if the MNG-806 fix is present
> -
>
> Key: MNG-2353
> URL: http://jira.codehaus.org/browse/MNG-2353
> Project: Maven 2
> Issue Type: Sub-task
> Components: Dependencies, Sites & Reporting
>Affects Versions: 2.0.4
> Environment: Windows XP SP2
>Reporter: Alejandro Scandroli
> Assigned To: Carlos Sanchez
>Priority: Minor
>
> mvn site:site fails generating the dependencies when the MNG-806 fix is
> present.
> I'm using this in my pom.xml
>
>
> sun.jdk
> tools
> 1.5
> system
> ${java.home}/../lib/tools.jar
>
> Here is the error log:
> (...)
> [INFO] Generate "Dependencies" report.
> [INFO]
>
> [ERROR] FATAL ERROR
> [INFO]
>
> [INFO] null
> [INFO]
>
> [INFO] Trace
> java.lang.NullPointerException
> at
> org.apache.maven.artifact.resolver.DefaultArtifactResolver.resolve(DefaultArtifactResolver.java:82)
> at
> org.apache.maven.artifact.resolver.DefaultArtifactResolver.resolve(DefaultArtifactResolver.java:63)
> at
> org.apache.maven.project.DefaultMavenProjectBuilder.findModelFromRepository(DefaultMavenProjectBuilder.java:467)
> at
> org.apache.maven.project.DefaultMavenProjectBuilder.buildFromRepository(DefaultMavenProjectBuilder.java:225)
> at
> org.apache.maven.report.projectinfo.DependenciesReport$DependenciesRenderer.getMavenProjectFromRepository(DependenciesReport.java:456)
> at
> org.apache.maven.report.projectinfo.DependenciesReport$DependenciesRenderer.printDescriptionsAndURLs(DependenciesReport.java:392)
> at
> org.apache.maven.report.projectinfo.DependenciesReport$DependenciesRenderer.printDescriptionsAndURLs(DependenciesReport.java:429)
> at
> org.apache.maven.report.projectinfo.DependenciesReport$DependenciesRenderer.renderBody(DependenciesReport.java:277)
> at
> org.apache.maven.reporting.AbstractMavenReportRenderer.render(AbstractMavenReportRenderer.java:65)
> at
> org.apache.maven.report.projectinfo.DependenciesReport.executeReport(DependenciesReport.java:97)
> at
> org.apache.maven.reporting.AbstractMavenReport.generate(AbstractMavenReport.java:101)
> at
> org.apache.maven.plugins.site.ReportDocumentRenderer.renderDocument(ReportDocumentRenderer.java:67)
> at
> org.apache.maven.doxia.siterenderer.DefaultSiteRenderer.renderModule(DefaultSiteRenderer.java:239)
> at
> org.apache.maven.doxia.siterenderer.DefaultSiteRenderer.render(DefaultSiteRenderer.java:115)
> at
> org.apache.maven.plugins.site.SiteMojo.renderLocale(SiteMojo.java:124)
> at org.apache.maven.plugins.site.SiteMojo.execute(SiteMojo.java:92)
> at
> org.apache.maven.plugin.DefaultPluginManager.executeMojo(DefaultPluginManager.java:412)
> at
> org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoals(DefaultLifecycleExecutor.java:534)
> at
> org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeStandaloneGoal(DefaultLifecycleExecutor.java:488)
> at
> org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoal(DefaultLifecycleExecutor.java:458)
> at
> org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoalAndHandleFailures(DefaultLifecycleExecutor.java:306)
> at
> org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeTaskSegments(DefaultLifecycleExecutor.java:273)
> at
> org.apache.maven.lifecycle.DefaultLifecycleExecutor.execute(DefaultLifecycleExecutor.java:140)
> at org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:322)
> at org.apache.maven.DefaultMaven.execute(DefaultMaven.java:115)
> at org.apache.maven.cli.MavenCli.main(MavenCli.java:256)
> 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.
[jira] Updated: (MNG-2356) Add timing information to integration tests
[ http://jira.codehaus.org/browse/MNG-2356?page=all ] Carlos Sanchez updated MNG-2356: Comment: was deleted > Add timing information to integration tests > --- > > Key: MNG-2356 > URL: http://jira.codehaus.org/browse/MNG-2356 > Project: Maven 2 > Issue Type: Improvement > Components: integration tests >Affects Versions: 2.0.4 >Reporter: Jerome Lacoste >Priority: Trivial > Fix For: 2.2 > > Attachments: MNG-2356.diff > > > Also document why using your installed maven to recompile this plugin is a > bad idea :) -- 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-2354) exclusion of a dependency prevents the dependency being added normally
[ http://jira.codehaus.org/browse/MNG-2354?page=all ] Carlos Sanchez updated MNG-2354: Comment: was deleted > exclusion of a dependency prevents the dependency being added normally > -- > > Key: MNG-2354 > URL: http://jira.codehaus.org/browse/MNG-2354 > Project: Maven 2 > Issue Type: Bug > Components: Dependencies >Reporter: Jorg Heymans > Assigned To: Carlos Sanchez > > Consider following usecase: > > commons-beanutils > commons-beanutils-core > 1.7.0 > > > commons-configuration > commons-configuration > 1.2 > > > commons-beanutils-core > commons-beanutils > > > Above pom configuration to me says: ignore the transitive dependency on > commons-beanutils-core brought in by commons-configurations because i would > like to define and use my own. However this configuration excludes > commons-beanutils-core completely, eg in a war build it's not included as a > dependency anymore. -- 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-1262) Add sources to commons-validator 1.3.1
[ http://jira.codehaus.org/browse/MAVENUPLOAD-1262?page=all ] Carlos Sanchez closed MAVENUPLOAD-1262. --- Assignee: Carlos Sanchez Resolution: Won't Fix Apache projects are synced from their repo, you have to aske them to put there the sources > Add sources to commons-validator 1.3.1 > -- > > Key: MAVENUPLOAD-1262 > URL: http://jira.codehaus.org/browse/MAVENUPLOAD-1262 > Project: maven-upload-requests > Issue Type: Bug >Reporter: Tomislav Stojcevich > Assigned To: Carlos Sanchez > Attachments: commons-validator-1.3.1-bundle.jar > > > Add sources only. -- 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: (CONTINUUM-1033) Unable to find text for key 'releaseProject.page.title' in ResourceBundles for locale 'en_US'
[ http://jira.codehaus.org/browse/CONTINUUM-1033?page=all ] Carlos Sanchez closed CONTINUUM-1033. - Assignee: Carlos Sanchez Resolution: Fixed Fix Version/s: 1.1 > Unable to find text for key 'releaseProject.page.title' in ResourceBundles > for locale 'en_US' > - > > Key: CONTINUUM-1033 > URL: http://jira.codehaus.org/browse/CONTINUUM-1033 > Project: Continuum > Issue Type: Bug > Components: Web - UI >Reporter: Edwin Punzalan > Assigned To: Carlos Sanchez > Fix For: 1.1 > > Attachments: CONTINUUM-1033-continuum-webapp.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: (MEAR-51) Exploded (unpacked) ear
[ http://jira.codehaus.org/browse/MEAR-51?page=comments#action_81915 ] Michael Lake commented on MEAR-51: -- I would also like this feature. you'll notice that if you do a "mvn compile" on an ear project, it will create an exploded ear in the target/ directory, but will not create a manifest file. if you use "mvn compile package" then it WILL create a zipped up ear which DOES have the manifest file. > Exploded (unpacked) ear > --- > > Key: MEAR-51 > URL: http://jira.codehaus.org/browse/MEAR-51 > Project: Maven 2.x Ear Plugin > Issue Type: New Feature >Affects Versions: 2.2 >Reporter: Maurice Zeijen > Assigned To: Stephane Nicoll > > It is great that you can unpack the modules within the ear. But it would be > also be great if the ear itself could also be delivered unpacked. At this > moment I could use the working directory but it doesn't get the Manifest file. -- 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: (MEAR-51) Exploded (unpacked) ear
[ http://jira.codehaus.org/browse/MEAR-51?page=comments#action_81916 ] Stephane Nicoll commented on MEAR-51: - yeah yeah ok. I get that. But what's the whole point of having the MANIFEST.MF file in the exploded ear. Is it actually used by the App server when it deploys the EAR? > Exploded (unpacked) ear > --- > > Key: MEAR-51 > URL: http://jira.codehaus.org/browse/MEAR-51 > Project: Maven 2.x Ear Plugin > Issue Type: New Feature >Affects Versions: 2.2 >Reporter: Maurice Zeijen > Assigned To: Stephane Nicoll > > It is great that you can unpack the modules within the ear. But it would be > also be great if the ear itself could also be delivered unpacked. At this > moment I could use the working directory but it doesn't get the Manifest file. -- 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: (MEV-459) Velocity should not depend on Velocity-dep
[ http://jira.codehaus.org/browse/MEV-459?page=comments#action_81917 ] Henri Yandell commented on MEV-459: --- They've a 1.5 in the works, but I don't think there are any plans for a 1.4.1. It'd be a bit odd for them to release a 1.4.1 - "re-releasing 1.4 as 1.4.1 so the Maven repository can have a new pom". So I think a 1.4-1 would be suitable here. Or we just leave it as a known problem and tell people to exclude the dependency. > Velocity should not depend on Velocity-dep > -- > > Key: MEV-459 > URL: http://jira.codehaus.org/browse/MEV-459 > Project: Maven Evangelism > Issue Type: Bug > Components: Dependencies >Reporter: Vincent Massol > > If a project is using ORO in version 2.0.8 then velocity-dep clashes with it > as it includes ORO with the original package name (a really really bad > practice). > For information, the problem arises for example with > Perl5Substitution.appendSubstitution(java.lang.StringBuffer stringBuffer, > org.apache.oro.text.regex.MatchResult matchResult, int i, java.lang.String > string, org.apache.oro.text.regex.PatternMatcher patternMatcher, > org.apache.oro.text.regex.Pattern pattern) which is valid in ORO 2.0.8 but > not in the version inside velocity-dep. > This problem should be raised against the Velocity project as it should not > be allowed to internally include another external package. -- 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-2367) Csharp dependencies are not inherited from dependencyManagement
[ http://jira.codehaus.org/browse/MNG-2367?page=all ] Dennis Lundberg updated MNG-2367: - Comment: was deleted > Csharp dependencies are not inherited from dependencyManagement > --- > > Key: MNG-2367 > URL: http://jira.codehaus.org/browse/MNG-2367 > Project: Maven 2 > Issue Type: Bug > Components: Sandbox > Environment: WIndows XP >Reporter: James Carpenter >Priority: Minor > > Csharp dependencies are not inherited from dependencyManagement. > As I am short on time, I havn't taken the time to figure out the bug. -- 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: (MEAR-51) Exploded (unpacked) ear
[ http://jira.codehaus.org/browse/MEAR-51?page=comments#action_81927 ] Maurice Zeijen commented on MEAR-51: I am not sure if the MANIFEST.MF file is used with an exploded ear. My JBoss 4.0.5.GA doesn't seem to find it a problem. But I don't know what the official JSR says about it. But there are more reasons to having an unpack option. 1. I would need to set the workDirectory property because the default workdirectory doesn't add the .ear on the end of the name. If I set the workDirectory then I lose the ability that the version is automatically added to the name. 2. The .ear file gets generated for nothing. If I want an unpacked ear directory then I probably don't need an .ear file. 3. I want the ear directory to be created in a different directory then the target directory. For instance in my jboss deploy directory so that I don't need to copy it manually. It just feels wrong to put the workDirectory there. 4. The workDirectory isn't meant to be used as an exploded ear. I can't depend on it to behave the same in future versions. > Exploded (unpacked) ear > --- > > Key: MEAR-51 > URL: http://jira.codehaus.org/browse/MEAR-51 > Project: Maven 2.x Ear Plugin > Issue Type: New Feature >Affects Versions: 2.2 >Reporter: Maurice Zeijen > Assigned To: Stephane Nicoll > > It is great that you can unpack the modules within the ear. But it would be > also be great if the ear itself could also be delivered unpacked. At this > moment I could use the working directory but it doesn't get the Manifest file. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Created: (MNG-2688) Cannot filter system properties in 2.0.4
Cannot filter system properties in 2.0.4
Key: MNG-2688
URL: http://jira.codehaus.org/browse/MNG-2688
Project: Maven 2
Issue Type: Bug
Components: Bootstrap & Build
Affects Versions: 2.0.4
Environment: Windows XP, sp2
Reporter: Chad Ellison
I would like to filter a system property, so that a property within my
application.properties files is replaced at runtime. The instructions at
http://maven.apache.org/guides/getting-started/index.html#How%20do%20I%20filter%20resource%20files?
are not working.
Specifically, in my application.propertiies file I have a variable defined
"command.line.prop=${command.line.prop}" and then when I run...
mvn process-resources "-Dcommand.line.prop=hello again"
... I would expect the property to be replaced by "hello again", but it is not.
It is worth noting that Java variables like ${java.version} are also not
filtered.
--
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: (MEAR-51) Exploded (unpacked) ear
[ http://jira.codehaus.org/browse/MEAR-51?page=comments#action_81931 ]
Stephane Nicoll commented on MEAR-51:
-
I am pretty sure the application server does not care at all if a manifest is
not present.
Regarding your questions:
# uh?
/opt/jboss/server/default/deploy/${pom.artifactId}-${pom.currentVersion}.ear
# True but then work directory should be the same or the unpack goal should
copy everything over the "exploded directory"
# Why?
# Yes it is. The EAR plugin is designed to build the EAR in this directory.
I can add an ear:exploded goal but I am not sure it will help.
Please provide more details, use case, etc and I will add the functionnality
for sure if it makes sense. For now, I don't really see a problem.
> Exploded (unpacked) ear
> ---
>
> Key: MEAR-51
> URL: http://jira.codehaus.org/browse/MEAR-51
> Project: Maven 2.x Ear Plugin
> Issue Type: New Feature
>Affects Versions: 2.2
>Reporter: Maurice Zeijen
> Assigned To: Stephane Nicoll
>
> It is great that you can unpack the modules within the ear. But it would be
> also be great if the ear itself could also be delivered unpacked. At this
> moment I could use the working directory but it doesn't get the Manifest file.
--
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: (MEAR-51) Exploded (unpacked) ear
[ http://jira.codehaus.org/browse/MEAR-51?page=comments#action_81935 ] Maurice Zeijen commented on MEAR-51: Thanks for your quick comment. Ok, maybe it isn't really needed. I see know that my points weren't that great... The only advantage that a separate option would have is that it would be clearer and easier for users to generate exploded ears (with the right name and such). I don't think that a separate goal would bring something. I was thinking more in the line of a configuration option. If set to true then the .ear file wouldn't get generated and the workDirectory would get the name from the finalName configuration option (or something like that). > Exploded (unpacked) ear > --- > > Key: MEAR-51 > URL: http://jira.codehaus.org/browse/MEAR-51 > Project: Maven 2.x Ear Plugin > Issue Type: New Feature >Affects Versions: 2.2 >Reporter: Maurice Zeijen > Assigned To: Stephane Nicoll > > It is great that you can unpack the modules within the ear. But it would be > also be great if the ear itself could also be delivered unpacked. At this > moment I could use the working directory but it doesn't get the Manifest file. -- 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-257) The perforce provider should provide an "update" functionality for the SCM plugin's "update" command that is semantically correct.
[ http://jira.codehaus.org/browse/SCM-257?page=comments#action_81936 ]
Dana Lacoste commented on SCM-257:
--
Although persist.checkout will work for keeping a clientspec persistent (after
the checkout command runs), it won't allow for using an existing clientspec in
that same checkout command.
In other words, if I want to use a clientspec that's already defined,
maven.scm.perforce.clientspec.name= will definitely work, but
executeCheckOutCommand() will (in the first try {} block) delete that
clientspec with its "p4 client -i" command.
So the test fails at step 4 above.
> The perforce provider should provide an "update" functionality for the SCM
> plugin's "update" command that is semantically correct.
> --
>
> Key: SCM-257
> URL: http://jira.codehaus.org/browse/SCM-257
> Project: Maven SCM
> Issue Type: Improvement
> Components: maven-scm-provider-perforce
> Environment: All OS, maven 2.x SCM plugin linked to perforce
>Reporter: Dana Lacoste
>
> The perforce provider implements the update command as a checkout.
> This is not semantically correct in the following situations:
> 1 - If no changes are pending, the update command should not do anything
> 2 - If some files are changed, only those files should be updated.
> (The checkout command checks out all files, regardless of what already exists)
> This is particularly daunting if (in my case :) there is a very large
> directory structure in perforce that does not change regularly (checking out
> a 4GB fileset that hasn't changed is, effectively, wasted time.)
> (As this is my first time using JIRA feel free to correct any of the settings
> I've made)
> Testing info:
> Although I don't have any JUnit experience, a test case can be made simply:
> 1 - create a perforce repository with two files in it (and configure maven to
> use it)
> 2 - run "mvn scm:checkout" to obtain the files
> 3 - modify one of the files on another system, check the modified file into
> perforce
> 4 - run "mvn scm:update" and only the modified file should be checked out.
> Implementation Ideas:
> Somehow the "scm:update" command will need to know that the files already
> exist. The most simple way is to require that ${P4CLIENT} be set and simply
> to run "p4 sync ..." in the directory involved (or, similarly, "p4 sync
> ${path}..." using the path that's defined in the scm URL) and to allow
> perforce to do the work of figuring out what's needed.
--
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-258) The perforce provider should be able to accept complex filespecs using a clientspec rather than the path in the SCM url
[ http://jira.codehaus.org/browse/SCM-258?page=comments#action_81937 ]
Dana Lacoste commented on SCM-258:
--
Unfortunately, the same problem as in the other issue occurs:
update and checkout are the same, and they both (in the first try {} block of
executeCheckoutCommand()) overwrite the existing clientspec with the fileset
information provided in the SCM URL
> The perforce provider should be able to accept complex filespecs using a
> clientspec rather than the path in the SCM url
> ---
>
> Key: SCM-258
> URL: http://jira.codehaus.org/browse/SCM-258
> Project: Maven SCM
> Issue Type: Improvement
> Components: maven-scm-provider-perforce
> Environment: All OS, Maven 2.x using the SCM plugin to talk to
> perforce
>Reporter: Dana Lacoste
>
> One of the strengths of perforce is the ability to do fairly complex actions
> with the clientspec.
> For example:
> 1 - Checkout two file structures into one location:
> //depot1/tree1/... //client/project/tree1
> //depot2/tree2/... //client/project/tree2
> 2 - Rename file structures at checkout time :
> //depot/tree/sample-configuration.xml //client/tree/configuration.xml
> The SCM URL format doesn't allow this (and implementing it would be difficult)
> Currently, the perforce provider doesn't seem to allow a way to use an
> existing clientspec (all codepaths seem to create a new clientspec based on
> the URL)
> If the provider could allow an existing clientspec to define the file
> structure, this functionality could be enabled.
> Testing:
> I don't have any JUnit experience, but I think this could be tested by:
> 1 - Create a clientspec that defines some complex content, for example:
> //depot/project/src/... //clientspec/project/src/...
> //ThirdParty/... //clientspec/project/ThirdParty/...
> 2 - run "mvn scm:checkout" and all files should be checked out.
> Implementation Ideas:
> I can see multiple ways of doing this, depending on the
> restrictions/conventions required
> A - Use the existing "bootstrap/target/checkout" dynamic directory structure
> - Using "p4 client -o" with the given/predefined/assumed clientspec,
> alter the p4_root (the line containing "Root:") and do a "p4 sync -f"
>(Definition of the clientspec ideas defined separately below)
> B - Assume the clientspec has a defined "Root:" and use that for the purposes
> of "locating" files (needed for tag/editing/checkin purposes)
> - As I'm only checking out, I really don't know how this would affect a
> checkin :)
> C - Separate from above, how to define which clientspec to use:
> - In the SCM URL, perhaps with scm:perforce:[EMAIL
> PROTECTED]:port:@clientspec_name
> (the second @ being a placeholder for a delimiter)
> - As an environment variable (perhaps the existing
> maven.scm.perforce.clientspec.name,
> enabling this functionality (re-use vs. re-create) with a different
> property
> - Defined in the settings.xml or in the pom.xml in the SCM configuration
> properties
> I'm sure more details will be required, this is only what I've identified
> within my particular situation.
--
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-1034) Create a link to project's site docs
Create a link to project's site docs
Key: CONTINUUM-1034
URL: http://jira.codehaus.org/browse/CONTINUUM-1034
Project: Continuum
Issue Type: Improvement
Reporter: Jim Crossley
Priority: Minor
It would be nice to be able to link to the project's site docs from the
continuum admin page. This would likely be the same link as ${project.url} in
the POM.
--
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: (MEAR-51) Exploded (unpacked) ear
[ http://jira.codehaus.org/browse/MEAR-51?page=comments#action_81943 ] Stephane Nicoll commented on MEAR-51: - I understand. Unfortunately, the default goal could not make this since it needs to generate an artifact and the finalName would clash. If we want an exploded form, we need a separate goal (see the war plugin for an example). Let me know what you think. > Exploded (unpacked) ear > --- > > Key: MEAR-51 > URL: http://jira.codehaus.org/browse/MEAR-51 > Project: Maven 2.x Ear Plugin > Issue Type: New Feature >Affects Versions: 2.2 >Reporter: Maurice Zeijen > Assigned To: Stephane Nicoll > > It is great that you can unpack the modules within the ear. But it would be > also be great if the ear itself could also be delivered unpacked. At this > moment I could use the working directory but it doesn't get the Manifest file. -- 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: (MASSEMBLY-153) files included with the tag have fileMode 204
[ http://jira.codehaus.org/browse/MASSEMBLY-153?page=comments#action_81945 ] Steven Coco commented on MASSEMBLY-153: --- Thanks for the workaround: I was stumped about this a moment ago. > files included with the tag have fileMode 204 > > > Key: MASSEMBLY-153 > URL: http://jira.codehaus.org/browse/MASSEMBLY-153 > Project: Maven 2.x Assembly Plugin > Issue Type: Bug >Affects Versions: 2.1 > Environment: linux >Reporter: Paul Jungwirth >Priority: Minor > > I'm trying to include files like this: > > > README > true > > > src/blah > > > I'm packaging them as both .tar.gz and .zip. In the tarball, the files wind > up with mode 0204: > --wr-- > In the zip file, they wind up with mode 1204: > --wr-T > Using a element of 644 does not fix the problem. This only happens > for files specified in , not . It happens whether I use > filtering or not. > These are pretty weird modes. I don't think this is a duplicate of > MASSEMBLY-75. It's not just losing the mode I set; it's assigning a very > peculiar mode as if with a mind of its own. > My umask is 0002. > Paul -- 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: (CONTINUUM-999) Successful builds are always followed by a failed build with no output
[ http://jira.codehaus.org/browse/CONTINUUM-999?page=all ] Brian Topping closed CONTINUUM-999. --- Resolution: Cannot Reproduce Seems to have gone away. > Successful builds are always followed by a failed build with no output > -- > > Key: CONTINUUM-999 > URL: http://jira.codehaus.org/browse/CONTINUUM-999 > Project: Continuum > Issue Type: Bug > Components: Core system >Affects Versions: 1.1 > Environment: Ubuntu >Reporter: Brian Topping > Attachments: Picture 2.png > > > Successful builds are always followed by a failed build with no output. See > attached picture. I can generate a patch, but where to start with this? > What schedules builds? Is there docs anywhere? -- 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-242) Replace the proxy url of the Download link into the absolute url
[ http://jira.codehaus.org/browse/MRM-242?page=comments#action_81950 ]
Jesse McConnell commented on MRM-242:
-
nap, having some problems with this part of the patch
${model.artifactId}-${model.version}.${model.packaging}
that can not be used reliably to generate the name of the file to pull down
ex maven-plugin is file extension .jar not .maven-plugin
could you resolve that while I work on the other part of this?
> Replace the proxy url of the Download link into the absolute url
>
>
> Key: MRM-242
> URL: http://jira.codehaus.org/browse/MRM-242
> Project: Archiva
> Issue Type: Improvement
> Components: web application
> Environment: Linux FC4, JDK1.5, Maven2.0.4
>Reporter: Napoleon Esmundo C. Ramirez
> Assigned To: Jesse McConnell
> Fix For: 1.0-beta-1
>
> Attachments: MRM-242-archiva.patch
>
>
> When browsing for artifacts in archiva, the Download link uses the proxy url.
> Since the artifacts are cached into archiva's managed repositories, the
> absolute url must be used at all times.
--
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-1035) Dependent builds not triggered via XMLRPC
Dependent builds not triggered via XMLRPC - Key: CONTINUUM-1035 URL: http://jira.codehaus.org/browse/CONTINUUM-1035 Project: Continuum Issue Type: Improvement Components: Core system Affects Versions: 1.2 Reporter: Brian Topping When running with CONTINUUM-232 changes applied, dependent builds are properly queued when the dependency is built. But this only happens from the webapp. It should also happen from XMLRPC -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Created: (MNG-2689) client-ejb dependency not working properly as reactor build
client-ejb dependency not working properly as reactor build
Key: MNG-2689
URL: http://jira.codehaus.org/browse/MNG-2689
Project: Maven 2
Issue Type: Bug
Components: Dependencies, Plugins and Lifecycle, POM, Reactor and
workspace
Affects Versions: 2.0.4
Reporter: Brian Topping
Attachments: it200x.tgz
I've attached an tarball in standard IT test format. :-)
If an artifact of ejb-client is built, it cannot be properly used
as a dependency by other builds in a reactor build without also having improper
access to the rest of the EJB libs.
The reason is somewhat disturbing, when the client project is built under
reactor, the compile plugin classpath includes the target/classes directory of
the EJB project. Take a look at it with -X:
{quote}
[INFO]
[INFO] Building client
[INFO]task-segment: [install]
[INFO]
[DEBUG] maven-jar-plugin: resolved to version 2.1 from repository central
[DEBUG] Retrieving parent-POM: org.apache.maven.plugins:maven-plugins::3 for
project: null:maven-jar-plugin:maven-plugin:2.1 from the repository.
[DEBUG] Retrieving parent-POM: org.apache.maven:maven-parent::4 for project:
org.apache.maven.plugins:maven-plugins:pom:3 from the repository.
[DEBUG] Retrieving parent-POM: org.apache:apache::3 for project:
org.apache.maven:maven-parent:pom:4 from the repository.
[DEBUG] Configuring mojo
'org.apache.maven.plugins:maven-resources-plugin:2.2:resources' -->
[DEBUG] (f) filters = []
[DEBUG] (f) outputDirectory =
/Users/briantopping/dev/it200x/client/target/classes
[DEBUG] (f) project = [EMAIL PROTECTED]
[DEBUG] (f) resources = [EMAIL PROTECTED]
[DEBUG] -- end configuration --
[INFO] [resources:resources]
[INFO] Using default encoding to copy filtered resources.
[DEBUG] org.apache.maven.it:client:jar:1-SNAPSHOT (selected for null)
[DEBUG] org.apache.maven.it:ejb:ejb-client:client:1-SNAPSHOT:compile
(selected for compile)
[DEBUG] junit:junit:jar:3.8.1:test (selected for test)
[DEBUG] Skipping disabled repository central
[DEBUG] ejb: using locally installed snapshot
[DEBUG] Configuring mojo
'org.apache.maven.plugins:maven-compiler-plugin:2.0.1:compile' -->
[DEBUG] (f) basedir = /Users/briantopping/dev/it200x/client
[DEBUG] (f) buildDirectory = /Users/briantopping/dev/it200x/client/target
[DEBUG] (f) classpathElements =
[/Users/briantopping/dev/it200x/client/target/classes,
/Users/briantopping/dev/it200x/ejb/target/classes]
[DEBUG] (f) compileSourceRoots =
[/Users/briantopping/dev/it200x/client/src/main/java]
[DEBUG] (f) compilerId = javac
[DEBUG] (f) debug = true
[DEBUG] (f) fork = false
[DEBUG] (f) optimize = false
[DEBUG] (f) outputDirectory =
/Users/briantopping/dev/it200x/client/target/classes
[DEBUG] (f) outputFileName = client-1-SNAPSHOT
[DEBUG] (f) projectArtifact = org.apache.maven.it:client:jar:1-SNAPSHOT
[DEBUG] (f) showDeprecation = false
[DEBUG] (f) showWarnings = false
[DEBUG] (f) staleMillis = 0
[DEBUG] (f) verbose = false
[DEBUG] -- end configuration --
[INFO] [compiler:compile]
[DEBUG] Using compiler 'javac'.
[DEBUG] Source directories:
[/Users/briantopping/dev/it200x/client/src/main/java]
[DEBUG] Classpath: [/Users/briantopping/dev/it200x/client/target/classes
/Users/briantopping/dev/it200x/ejb/target/classes]
[DEBUG] Output directory: /Users/briantopping/dev/it200x/client/target/classes
[DEBUG] Classpath:
[DEBUG] /Users/briantopping/dev/it200x/client/target/classes
*[DEBUG] /Users/briantopping/dev/it200x/ejb/target/classes*
[DEBUG] Source roots:
[DEBUG] /Users/briantopping/dev/it200x/client/src/main/java
Compiling 2 source files to /Users/briantopping/dev/it200x/client/target/classes
{quote}
Note the boldfaced text.
Now let's try again, but inside the client directory of the attached IT test:
{quote}
[INFO]
[INFO] Building client
[INFO]task-segment: [clean, install]
[INFO]
[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] Retrieving parent-POM: org.apache.maven:maven::2.0 for project:
org.apache.maven:maven-plugin-api:jar:2.0 from the repository.
[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
[jira] Created: (MECLIPSE-203) option to make dirs in resources directory view as classpath
option to make dirs in resources directory view as classpath Key: MECLIPSE-203 URL: http://jira.codehaus.org/browse/MECLIPSE-203 Project: Maven 2.x Eclipse Plugin Issue Type: Improvement Environment: windows, eclipse 3.2, maven 2.0.4 Reporter: Brill Pappin Older versions of this plugin used to set up the src/main/resources as a classpath so the directories looked like packages. Currently they are set up to look like a navigator view. I liked the old way of displaying, particularly since the resources *are* in the classpath. I'd like the there to be an option to allow directories to be shown as a package rather than a dir tree. I'll even make the mod is someone will apply the 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] Created: (MRM-246) No message displayed for unsuccessful Archiva login attempts (intermittent)
No message displayed for unsuccessful Archiva login attempts (intermittent) --- Key: MRM-246 URL: http://jira.codehaus.org/browse/MRM-246 Project: Archiva Issue Type: Bug Reporter: Maria Odea Ching Steps to re-produce the problem: 1. Opened Archiva main page 2. Clicked 'Login' link 3. Entered User Name & INCORRECT Password & clicked 'Login' button It displays message 'You have entered an incorrect username and/or password' for the first few invalid attemps 'Authentication Failed'. After 3 invalid attempts, there is no authentication error message displayed. It just displays back the main Archiva page. -- 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-246) No message displayed for unsuccessful Archiva login attempts (intermittent)
[ http://jira.codehaus.org/browse/MRM-246?page=comments#action_81958 ] Maria Odea Ching commented on MRM-246: -- Fixed at revision 483341. Thanks! :) > No message displayed for unsuccessful Archiva login attempts (intermittent) > --- > > Key: MRM-246 > URL: http://jira.codehaus.org/browse/MRM-246 > Project: Archiva > Issue Type: Bug >Reporter: Maria Odea Ching > Assigned To: Maria Odea Ching > > Steps to re-produce the problem: > 1. Opened Archiva main page > 2. Clicked 'Login' link > 3. Entered User Name & INCORRECT Password & clicked 'Login' button > It displays message 'You have entered an incorrect username and/or password' > for the first few invalid attemps 'Authentication Failed'. After 3 invalid > attempts, there is no authentication error message displayed. It just > displays back the main Archiva page. -- 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: (MRM-246) No message displayed for unsuccessful Archiva login attempts (intermittent)
[ http://jira.codehaus.org/browse/MRM-246?page=all ] Maria Odea Ching updated MRM-246: - Description: Steps to re-produce the problem: 1. Opened Archiva main page 2. Clicked 'Login' link 3. Entered User Name & INCORRECT Password & clicked 'Login' button It displays message 'You have entered an incorrect username and/or password' for the first few invalid attemps. After 3 invalid attempts, there is no authentication error message displayed. It just displays back the main Archiva page. was: Steps to re-produce the problem: 1. Opened Archiva main page 2. Clicked 'Login' link 3. Entered User Name & INCORRECT Password & clicked 'Login' button It displays message 'You have entered an incorrect username and/or password' for the first few invalid attemps 'Authentication Failed'. After 3 invalid attempts, there is no authentication error message displayed. It just displays back the main Archiva page. > No message displayed for unsuccessful Archiva login attempts (intermittent) > --- > > Key: MRM-246 > URL: http://jira.codehaus.org/browse/MRM-246 > Project: Archiva > Issue Type: Bug >Reporter: Maria Odea Ching > Assigned To: Maria Odea Ching > > Steps to re-produce the problem: > 1. Opened Archiva main page > 2. Clicked 'Login' link > 3. Entered User Name & INCORRECT Password & clicked 'Login' button > It displays message 'You have entered an incorrect username and/or password' > for the first few invalid attemps. After 3 invalid attempts, there is no > authentication error message displayed. It just displays back the main > Archiva page. -- 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-183) should report all unresolved dependencies, not just the first encountered.
should report all unresolved dependencies, not just the first encountered. -- Key: MRELEASE-183 URL: http://jira.codehaus.org/browse/MRELEASE-183 Project: Maven 2.x Release Plugin Issue Type: Improvement Affects Versions: 2.0-beta-4 Reporter: Brett Porter this would facilitate using dryRun to find all snapshots. -- 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: (MRELEASE-183) should report all unresolved dependencies, not just the first encountered.
[ http://jira.codehaus.org/browse/MRELEASE-183?page=all ] Brett Porter updated MRELEASE-183: -- Fix Version/s: 2.0-beta-5 > should report all unresolved dependencies, not just the first encountered. > -- > > Key: MRELEASE-183 > URL: http://jira.codehaus.org/browse/MRELEASE-183 > Project: Maven 2.x Release Plugin > Issue Type: Improvement >Affects Versions: 2.0-beta-4 >Reporter: Brett Porter > Fix For: 2.0-beta-5 > > > this would facilitate using dryRun to find all snapshots. -- 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: (CONTINUUM-125) Export/Import projects, configuration and history
[ http://jira.codehaus.org/browse/CONTINUUM-125?page=all ] Brett Porter closed CONTINUUM-125. -- Assignee: Brett Porter Resolution: Fixed continuum-data-management > Export/Import projects, configuration and history > - > > Key: CONTINUUM-125 > URL: http://jira.codehaus.org/browse/CONTINUUM-125 > Project: Continuum > Issue Type: Task > Components: Core system, XMLRPC Interface >Reporter: Trygve Laugstol > Assigned To: Brett Porter > Fix For: 1.1 > > -- 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-246) No message displayed for unsuccessful Archiva login attempts (intermittent)
[ http://jira.codehaus.org/browse/MRM-246?page=all ] Maria Odea Ching closed MRM-246. Resolution: Fixed > No message displayed for unsuccessful Archiva login attempts (intermittent) > --- > > Key: MRM-246 > URL: http://jira.codehaus.org/browse/MRM-246 > Project: Archiva > Issue Type: Bug >Reporter: Maria Odea Ching > Assigned To: Maria Odea Ching > > Steps to re-produce the problem: > 1. Opened Archiva main page > 2. Clicked 'Login' link > 3. Entered User Name & INCORRECT Password & clicked 'Login' button > It displays message 'You have entered an incorrect username and/or password' > for the first few invalid attemps. After 3 invalid attempts, there is no > authentication error message displayed. It just displays back the main > Archiva page. -- 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-242) Replace the proxy url of the Download link into the absolute url
[ http://jira.codehaus.org/browse/MRM-242?page=comments#action_81961 ] Napoleon Esmundo C. Ramirez commented on MRM-242: - Ok, I'll revise my patch for that. I'll try to include a fix for the authz if I happen to pass along the code. Thanks! :) > Replace the proxy url of the Download link into the absolute url > > > Key: MRM-242 > URL: http://jira.codehaus.org/browse/MRM-242 > Project: Archiva > Issue Type: Improvement > Components: web application > Environment: Linux FC4, JDK1.5, Maven2.0.4 >Reporter: Napoleon Esmundo C. Ramirez > Assigned To: Jesse McConnell > Fix For: 1.0-beta-1 > > Attachments: MRM-242-archiva.patch > > > When browsing for artifacts in archiva, the Download link uses the proxy url. > Since the artifacts are cached into archiva's managed repositories, the > absolute url must be used at all times. -- 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
