[jira] (MNG-2199) Version ranges not supported for parent artifacts
[
https://jira.codehaus.org/browse/MNG-2199?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Christian Schulte updated MNG-2199:
---
Attachment: MNG-2199.patch
Updated the patch to additionally validate a 'version' to not use expressions.
{code}
Script started on Wed Sep 19 08:32:30 2012
$ cat pom.xml
org.apache
apache
[,11]
4.0.0
mng2199
jar
$ mvn clean
[INFO] Scanning for projects...
[ERROR] The build could not read 1 project -> [Help 1]
[ERROR]
[ERROR] The project org.apache:mng2199:11 (/tmp/mng2199/pom.xml) has 1 error
[ERROR] 'version' must be a constant. @
org.apache:mng2199:[unknown-version], /tmp/mng2199/pom.xml, line 2, column 11
[ERROR]
[ERROR] To see the full stack trace of the errors, re-run Maven with the -e
switch.
[ERROR] Re-run Maven using the -X switch to enable full debug logging.
[ERROR]
[ERROR] For more information about the errors and possible solutions, please
read the following articles:
[ERROR] [Help 1]
http://cwiki.apache.org/confluence/display/MAVEN/ProjectBuildingException
$ ^D
Script done on Wed Sep 19 08:32:42 2012
{code}
{code}
Script started on Wed Sep 19 08:33:36 2012
$ cat pom.xml
org.apache
apache
[,11]
4.0.0
mng2199
jar
1.0-${expression}-SNAPSHOT
$ mvn clean
[INFO] Scanning for projects...
[ERROR] The build could not read 1 project -> [Help 1]
[ERROR]
[ERROR] The project org.apache:mng2199:1.0-${expression}-SNAPSHOT
(/tmp/mng2199/pom.xml) has 1 error
[ERROR] 'version' contains an expression but must be a constant. @ line 2,
column 11
[ERROR]
[ERROR] To see the full stack trace of the errors, re-run Maven with the -e
switch.
[ERROR] Re-run Maven using the -X switch to enable full debug logging.
[ERROR]
[ERROR] For more information about the errors and possible solutions, please
read the following articles:
[ERROR] [Help 1]
http://cwiki.apache.org/confluence/display/MAVEN/ProjectBuildingException
$ ^D
Script done on Wed Sep 19 08:33:47 2012
{code}
> Version ranges not supported for parent artifacts
> -
>
> Key: MNG-2199
> URL: https://jira.codehaus.org/browse/MNG-2199
> Project: Maven 2 & 3
> Issue Type: Wish
> Components: Inheritance and Interpolation, POM, Reactor and workspace
>Affects Versions: 2.0.3
>Reporter: Christian Schulte
> Fix For: Issues to be reviewed for 3.x
>
> Attachments: MNG-2199.patch, MNG-2199.patch, MNG-2199.patch,
> MNG-2199.patch
>
>
> It would be great if Maven supports version ranges when specifying parent
> artifacts in a multi-module build. Currently this does not work.
>
> artifactId
> groupId
> [2.0, 2.0.1]
>
> [INFO] Scanning for projects...
> Downloading: http://repo1.maven.org/maven2/groupId/artifactId/[2.0,
> 2.0.1]/artifactId-[2.0, 2.0.1].pom
> Additionally it would be great if this
>
> artifactId
> groupId
> [2.0, ${pom.version}]
>
> [INFO] Scanning for projects...
> Downloading: http://repo1.maven.org/maven2/groupId/artifactId/[2.0,
> ${pom.version}]/artifactId-[2.0, ${pom.version}].pom
> would also work, if the version is specified in the same pom.xml which
> defines this parent definition.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://jira.codehaus.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] (MRELEASE-543) prepare-with-pom : inherited dependencies exclusion are lost in release-pom.xml
[ https://jira.codehaus.org/browse/MRELEASE-543?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=308943#comment-308943 ] Bartosz Radaczynski commented on MRELEASE-543: -- Does this also impact transitive exclusions or just inherited ones? > prepare-with-pom : inherited dependencies exclusion are lost in > release-pom.xml > --- > > Key: MRELEASE-543 > URL: https://jira.codehaus.org/browse/MRELEASE-543 > Project: Maven 2.x Release Plugin > Issue Type: Bug > Components: prepare-with-pom >Affects Versions: 2.0 > Environment: Maven 2.2.1 >Reporter: Thomas Sauzedde > Attachments: sample-projects.tgz > > > Like in the provided sample projects, I have the following scenario : 3 > modules (sibling) with the following inheritage graph : > grandfather <=== father <=== child > - grandfather (pom module) has > - a dependencyManagement block with some exclusions > - a pluginManagement block > - father (pom module) adds a plugins block to configure the compiler plugin > - child is a basic (empty) jar module > when mvn release:prepare-with-pom is performed on "child" the checked-in > (svn) release-pom.xml has all the dependencies resolved BUT my exclusions > defined in "grandfather" are lost :-( > To reproduce this with the provided sample projects : > - perform a mvn:install on grandfather & father > - import "child" in your svn repo > - change the scm block on "child" in order to checkout/in from your svn > - perform a mvn release:prepare-with-pom > You will see that in your tagged release-pom.xml the exclusions are lost. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://jira.codehaus.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] (MRELEASE-543) prepare-with-pom : inherited dependencies exclusion are lost in release-pom.xml
[ https://jira.codehaus.org/browse/MRELEASE-543?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=308941#comment-308941 ] Bartosz Radaczynski commented on MRELEASE-543: -- Is this issue fixed in any version of the release plugin? > prepare-with-pom : inherited dependencies exclusion are lost in > release-pom.xml > --- > > Key: MRELEASE-543 > URL: https://jira.codehaus.org/browse/MRELEASE-543 > Project: Maven 2.x Release Plugin > Issue Type: Bug > Components: prepare-with-pom >Affects Versions: 2.0 > Environment: Maven 2.2.1 >Reporter: Thomas Sauzedde > Attachments: sample-projects.tgz > > > Like in the provided sample projects, I have the following scenario : 3 > modules (sibling) with the following inheritage graph : > grandfather <=== father <=== child > - grandfather (pom module) has > - a dependencyManagement block with some exclusions > - a pluginManagement block > - father (pom module) adds a plugins block to configure the compiler plugin > - child is a basic (empty) jar module > when mvn release:prepare-with-pom is performed on "child" the checked-in > (svn) release-pom.xml has all the dependencies resolved BUT my exclusions > defined in "grandfather" are lost :-( > To reproduce this with the provided sample projects : > - perform a mvn:install on grandfather & father > - import "child" in your svn repo > - change the scm block on "child" in order to checkout/in from your svn > - perform a mvn release:prepare-with-pom > You will see that in your tagged release-pom.xml the exclusions are lost. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://jira.codehaus.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] (MCHANGES-288) JIRA url not fully respected
Bruno Marti created MCHANGES-288:
Summary: JIRA url not fully respected
Key: MCHANGES-288
URL: https://jira.codehaus.org/browse/MCHANGES-288
Project: Maven 2.x Changes Plugin
Issue Type: Bug
Components: jira
Affects Versions: 2.8
Environment: OS XP, maven 3.0.4
Reporter: Bruno Marti
Issue url is not fully used by maven-changes-plugin:2.8
have following issue url:
{quote}
JIRA
https://my.ch/prod/jira/?pid=1
{quote}
with changes-plugin:2.7.1 works well:
{quote}
[INFO] Generating "JIRA Report" report--- maven-changes-plugin:2.7.1
[DEBUG] JIRA lives at: https://my.ch/prod/jira
[DEBUG] Login URL:
https://my.ch/prod/jira/login.jsp?os_destination=/secure/&os_username=*&os_password=*
[DEBUG] Successfully logged in into JIRA.
{quote}
BUT with changes-plugin:2.8, got error:
{quote}
[INFO] Generating "JIRA Report" report--- maven-changes-plugin:2.8
[DEBUG] JIRA lives at: https://my.ch
[DEBUG] Login URL:
https://my.ch/login.jsp?os_destination=/secure/&os_username=*&os_password=*
[ERROR] Error trying to login into JIRA.
java.net.SocketException: Connection reset
{quote}
Problem is, that the additional context */prod/jira/* gets lost.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://jira.codehaus.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] (MSHARED-243) add a way to calculate diffs of a directory at 2 different times
[ https://jira.codehaus.org/browse/MSHARED-243?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mark Struberg closed MSHARED-243. - Resolution: Fixed Implemented in DirectoryScanner#diffIncludedFiles( String[] oldFiles ); This method returns a ScanResult which currently contains the lists of added and removed files. > add a way to calculate diffs of a directory at 2 different times > > > Key: MSHARED-243 > URL: https://jira.codehaus.org/browse/MSHARED-243 > Project: Maven Shared Components > Issue Type: New Feature > Components: maven-shared-utils >Reporter: Mark Struberg >Assignee: Mark Struberg > > For implementing the incremental build it should be possible to detect which > files got created by a certain mojo execution. > An example would be the maven-compiler-plugin which currently doesn't remove > class files for Java sources which got deleted. > The idea is to introduce a helper which can capture a snapshot of a certain > directory (e.g. target/classes), then you do the mojo work (javac invocation > with all source files) and take a capture of that very directory again. > The tool will allow you to take a 'diff' and store the names of all the added > files to a file in target/... > The next time you invoke a build you can delete all those created classes by > this very mojo-execution and so you do not have any left-overs. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://jira.codehaus.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] (MSHARED-243) add a way to calculate diffs of a directory at 2 different times
[ https://jira.codehaus.org/browse/MSHARED-243?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mark Struberg reassigned MSHARED-243: - Assignee: Mark Struberg > add a way to calculate diffs of a directory at 2 different times > > > Key: MSHARED-243 > URL: https://jira.codehaus.org/browse/MSHARED-243 > Project: Maven Shared Components > Issue Type: New Feature > Components: maven-shared-utils >Reporter: Mark Struberg >Assignee: Mark Struberg > > For implementing the incremental build it should be possible to detect which > files got created by a certain mojo execution. > An example would be the maven-compiler-plugin which currently doesn't remove > class files for Java sources which got deleted. > The idea is to introduce a helper which can capture a snapshot of a certain > directory (e.g. target/classes), then you do the mojo work (javac invocation > with all source files) and take a capture of that very directory again. > The tool will allow you to take a 'diff' and store the names of all the added > files to a file in target/... > The next time you invoke a build you can delete all those created classes by > this very mojo-execution and so you do not have any left-overs. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://jira.codehaus.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] (DOXIA-472) No page title is set when using markdown
[ https://jira.codehaus.org/browse/DOXIA-472?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=308912#comment-308912 ] Jason Duke commented on DOXIA-472: -- This would be really useful. > No page title is set when using markdown > > > Key: DOXIA-472 > URL: https://jira.codehaus.org/browse/DOXIA-472 > Project: Maven Doxia > Issue Type: Bug > Components: Module - Markdown >Affects Versions: 1.3 >Reporter: Klaus Reimer >Priority: Minor > > No page title is created for pages which are defined with the markup language > "markdown". A page in a project named "Test" opened with Chrome for example > has the browser title "Test - - Chrome" and the browser tab is labeled with > "Test - ". > I recommend using the first headline in the markdown file as a page title. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://jira.codehaus.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] (SUREFIRE-800) redirectTestOutputToFile is not taken into account in all cases with JUnit47 provider
[
https://jira.codehaus.org/browse/SUREFIRE-800?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=308907#comment-308907
]
Kristian Rosenvold commented on SUREFIRE-800:
-
I applied the patch and the testcase to a branch on github. I added your
testclass to
surefire-integration-tests/src/test/resources/junit47-redirect-output
If you run:
git clone --branch=SUREFIRE800 https://github.com/krosenvold/maven-surefire
cd
maven-surefire/surefire-integration-tests/src/test/resources/junit47-redirect-output
mvn -Dsurefire.version=2.12.3 -Dtest=Test0 test
cat target/surefire-reports/junit47ConsoleOutput.Test0-output.txt
If I build the version with your patch, nothing really changes in the status of
the console output and the output text files either ?
> redirectTestOutputToFile is not taken into account in all cases with JUnit47
> provider
> -
>
> Key: SUREFIRE-800
> URL: https://jira.codehaus.org/browse/SUREFIRE-800
> Project: Maven Surefire
> Issue Type: Bug
> Components: Junit 4.7+ (parallel) support
>Affects Versions: 2.10
> Environment: all
>Reporter: nkeywal
>Assignee: Kristian Rosenvold
> Fix For: 2.13
>
> Attachments: 800.v1.patch
>
>
> With the following class:
> {noformat}
> public class Test0 {
> public Test0(){
> System.out.println("Constructor");
> }
> @Test
> public void testT0() throws Exception {
> System.out.println("testT0");
> }
> @Test
> public void testT1() throws Exception {
> System.out.println("testT1");
> }
> @BeforeClass
> public static void setUpBeforeClass() throws Exception {
> System.out.println("setUpBeforeClass");
> }
> @AfterClass
> public static void tearDownAfterClass() throws Exception {
> System.out.println("tearDownAfterClass");
> }
> @Before
> public void setUp() throws Exception {
> System.out.println("setUp");
> }
> @After
> public void tearDown() throws Exception {
> System.out.println("tearDown");
> }
> }
> {noformat}
> Some elements of the output are not redirected with JUNit47.
> {noformat}
> Concurrency config is parallel='none', perCoreThreadCount=true,
> threadCount=2, useUnlimitedThreads=false
> setUpBeforeClass
> Constructor
> Constructor
> tearDownAfterClass
> Running Test0
> Tests run: 2, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 0.01 sec
> {noformat}
> While it's ok with with JUNit4:
> {noformat}
> ---
> T E S T S
> ---
> Running Test0
> Tests run: 2, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 0.09 sec
> {noformat}
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://jira.codehaus.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] (SUREFIRE-909) Wrong elapsed time calculation
[ https://jira.codehaus.org/browse/SUREFIRE-909?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=308893#comment-308893 ] Kristian Rosenvold commented on SUREFIRE-909: - It has become somewhat of a surefire tradition to break this logic every time it is touched. Hopefully this last refactoring simplified it enough to make sure it does not break again. Fixed in 8dbde6de81cddd7335a5768dc22d9c414db6ef86, this time with a Unit test. > Wrong elapsed time calculation > --- > > Key: SUREFIRE-909 > URL: https://jira.codehaus.org/browse/SUREFIRE-909 > Project: Maven Surefire > Issue Type: Bug > Components: Junit 4.x support >Affects Versions: 2.12.3 > Environment: linux, likely others >Reporter: nkeywal > Fix For: 2.13 > > > It's a regression in 2.12.3 vs. the previous versions. > See "Time elapsed: 251992 sec" > 2.12.3 > Running my.Test > Tests run: 1, Failures: 1, Errors: 0, Skipped: 0, Time elapsed: 252.358 sec > <<< FAILURE! > test(my.Test) Time elapsed: 251992 sec <<< FAILURE! > java.lang.AssertionError: expected array was null > 2.10 or 2.11 or 2.12.1 or 2.12.2 > Tests run: 1, Failures: 1, Errors: 0, Skipped: 0, Time elapsed: 252.444 sec > <<< FAILURE! > test(my.Test) Time elapsed: 252.194 sec <<< FAILURE! > java.lang.AssertionError: expected array was null -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://jira.codehaus.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] (MASSEMBLY-343) add symbolic links managment
[ https://jira.codehaus.org/browse/MASSEMBLY-343?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=308883#comment-308883 ] Ahmed El-Madhoun commented on MASSEMBLY-343: I kind of figured that out once I looked more into the patch and this case. I am thinking of porting assembly plugin into JDK7 with ability to automatically package symlinks, would you be interested in helping out? > add symbolic links managment > > > Key: MASSEMBLY-343 > URL: https://jira.codehaus.org/browse/MASSEMBLY-343 > Project: Maven 2.x Assembly Plugin > Issue Type: Wish >Affects Versions: 2.2-beta-2 > Environment: linux, ubuntu >Reporter: Godet Gilles > Attachments: MASSEMBLY-343_maven-assembly-plugin_fixed.patch, > MASSEMBLY-343_maven-assembly-plugin.patch > > > i need to buid archives ( tar for example ) with symbolic links > the plugin build an archive with a file containing the destination of the > link, not the link itself > => the plugin need an option to know if deferencement of links is needed > this is just like -h option of tar > -h, --dereference > don't dump symlinks; dump the files they point to > actually, if you do an archive of /lib, for example, many file will be in > double with différent names. extract of archive will not be the exactly the > same as the source of the archive. => this is a test ! -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://jira.codehaus.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] (MASSEMBLY-343) add symbolic links managment
[ https://jira.codehaus.org/browse/MASSEMBLY-343?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=308882#comment-308882 ] Zuhayr Khan commented on MASSEMBLY-343: --- It sounds like you're hoping that the assembly plugin will look at symlinks on your file-system and include them within the assembled package? This use case is what the discussion on PLXCOMP-117 covers. In summary, because of the lack of system-agnostic support for symbolic links (pre Java 7?) plexus-io doesn't read/identify symlinks in this manner. The patch here simply allows you to configure symlinks within the assembly-definition such that they are recorded in the tar/zip file as symlinks. If I've understood your use case correctly, to take advantage of this, you'd need to add a "symlinks" element (see my initial comment on this) to your assembly-definition that correspond to the actual symlinks on your file system. Hope that helps. > add symbolic links managment > > > Key: MASSEMBLY-343 > URL: https://jira.codehaus.org/browse/MASSEMBLY-343 > Project: Maven 2.x Assembly Plugin > Issue Type: Wish >Affects Versions: 2.2-beta-2 > Environment: linux, ubuntu >Reporter: Godet Gilles > Attachments: MASSEMBLY-343_maven-assembly-plugin_fixed.patch, > MASSEMBLY-343_maven-assembly-plugin.patch > > > i need to buid archives ( tar for example ) with symbolic links > the plugin build an archive with a file containing the destination of the > link, not the link itself > => the plugin need an option to know if deferencement of links is needed > this is just like -h option of tar > -h, --dereference > don't dump symlinks; dump the files they point to > actually, if you do an archive of /lib, for example, many file will be in > double with différent names. extract of archive will not be the exactly the > same as the source of the archive. => this is a test ! -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://jira.codehaus.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] (MNG-2199) Version ranges not supported for parent artifacts
[
https://jira.codehaus.org/browse/MNG-2199?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Christian Schulte updated MNG-2199:
---
Attachment: MNG-2199.patch
Updated the patch one more time. This patch adds support for
{code}
gid
aid
Maven version range syntax, e.g. [1.0, 2.0)
{code}
It will fail the build whenever a child references a parent that way without
defining a version. Error message would be: 'Child POM
gid:aid:[unknown-version] cannot inherit version [1.0,2.0) from parent. Must
define a version explicitly.'
One thing I would want this patch to do additionally, is validation of the
version ranges in use. I did not find methods at interface
'org.sonatype.aether.version.VersionRange' to allow querying for 'isBounded' /
'isUpperBounded' / 'isLowerBounded' which would be needed for this.
> Version ranges not supported for parent artifacts
> -
>
> Key: MNG-2199
> URL: https://jira.codehaus.org/browse/MNG-2199
> Project: Maven 2 & 3
> Issue Type: Wish
> Components: Inheritance and Interpolation, POM, Reactor and workspace
>Affects Versions: 2.0.3
>Reporter: Christian Schulte
> Fix For: Issues to be reviewed for 3.x
>
> Attachments: MNG-2199.patch, MNG-2199.patch, MNG-2199.patch
>
>
> It would be great if Maven supports version ranges when specifying parent
> artifacts in a multi-module build. Currently this does not work.
>
> artifactId
> groupId
> [2.0, 2.0.1]
>
> [INFO] Scanning for projects...
> Downloading: http://repo1.maven.org/maven2/groupId/artifactId/[2.0,
> 2.0.1]/artifactId-[2.0, 2.0.1].pom
> Additionally it would be great if this
>
> artifactId
> groupId
> [2.0, ${pom.version}]
>
> [INFO] Scanning for projects...
> Downloading: http://repo1.maven.org/maven2/groupId/artifactId/[2.0,
> ${pom.version}]/artifactId-[2.0, ${pom.version}].pom
> would also work, if the version is specified in the same pom.xml which
> defines this parent definition.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://jira.codehaus.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] (MNG-2199) Version ranges not supported for parent artifacts
[
https://jira.codehaus.org/browse/MNG-2199?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=308872#comment-308872
]
Christian Schulte commented on MNG-2199:
[Super-POM
History|http://svn.apache.org/viewvc/maven/maven-3/trunk/maven-model-builder/src/main/resources/org/apache/maven/model/pom-4.0.0.xml?view=log]
- [use proper
CNAME|http://svn.apache.org/viewvc/maven/maven-3/trunk/maven-model-builder/src/main/resources/org/apache/maven/model/pom-4.0.0.xml?r1=1155270&r2=1160922&diff_format=h]
- [going back to assembly beta-1 as there is an important regression in
assembly:attached|http://svn.apache.org/viewvc/maven/maven-3/trunk/maven-model-builder/src/main/resources/org/apache/maven/model/pom-4.0.0.xml?r1=639019&r2=639744&diff_format=h]
- [try using repo1 again to see if it avoids the 503
errors|http://svn.apache.org/viewvc/maven/maven-3/trunk/maven-model-builder/src/main/resources/org/apache/maven/model/pom-4.0.0.xml?r1=320991&r2=326009&diff_format=h]
- [change main repo until we stabilise
maven.org|http://svn.apache.org/viewvc/maven/maven-3/trunk/maven-model-builder/src/main/resources/org/apache/maven/model/pom-4.0.0.xml?r1=292103&r2=320693&diff_format=h]
> Version ranges not supported for parent artifacts
> -
>
> Key: MNG-2199
> URL: https://jira.codehaus.org/browse/MNG-2199
> Project: Maven 2 & 3
> Issue Type: Wish
> Components: Inheritance and Interpolation, POM, Reactor and workspace
>Affects Versions: 2.0.3
>Reporter: Christian Schulte
> Fix For: Issues to be reviewed for 3.x
>
> Attachments: MNG-2199.patch, MNG-2199.patch
>
>
> It would be great if Maven supports version ranges when specifying parent
> artifacts in a multi-module build. Currently this does not work.
>
> artifactId
> groupId
> [2.0, 2.0.1]
>
> [INFO] Scanning for projects...
> Downloading: http://repo1.maven.org/maven2/groupId/artifactId/[2.0,
> 2.0.1]/artifactId-[2.0, 2.0.1].pom
> Additionally it would be great if this
>
> artifactId
> groupId
> [2.0, ${pom.version}]
>
> [INFO] Scanning for projects...
> Downloading: http://repo1.maven.org/maven2/groupId/artifactId/[2.0,
> ${pom.version}]/artifactId-[2.0, ${pom.version}].pom
> would also work, if the version is specified in the same pom.xml which
> defines this parent definition.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://jira.codehaus.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] (MNG-2199) Version ranges not supported for parent artifacts
[
https://jira.codehaus.org/browse/MNG-2199?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Paul Benedict updated MNG-2199:
---
Issue Type: Wish (was: Bug)
Changing issue type from "Bug" to "Wish"
> Version ranges not supported for parent artifacts
> -
>
> Key: MNG-2199
> URL: https://jira.codehaus.org/browse/MNG-2199
> Project: Maven 2 & 3
> Issue Type: Wish
> Components: Inheritance and Interpolation, POM, Reactor and workspace
>Affects Versions: 2.0.3
>Reporter: Christian Schulte
> Fix For: Issues to be reviewed for 3.x
>
> Attachments: MNG-2199.patch, MNG-2199.patch
>
>
> It would be great if Maven supports version ranges when specifying parent
> artifacts in a multi-module build. Currently this does not work.
>
> artifactId
> groupId
> [2.0, 2.0.1]
>
> [INFO] Scanning for projects...
> Downloading: http://repo1.maven.org/maven2/groupId/artifactId/[2.0,
> 2.0.1]/artifactId-[2.0, 2.0.1].pom
> Additionally it would be great if this
>
> artifactId
> groupId
> [2.0, ${pom.version}]
>
> [INFO] Scanning for projects...
> Downloading: http://repo1.maven.org/maven2/groupId/artifactId/[2.0,
> ${pom.version}]/artifactId-[2.0, ${pom.version}].pom
> would also work, if the version is specified in the same pom.xml which
> defines this parent definition.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://jira.codehaus.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] (MNG-2199) Version ranges not supported for parent artifacts
[
https://jira.codehaus.org/browse/MNG-2199?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=308865#comment-308865
]
Paul Benedict commented on MNG-2199:
I don't think parent versions should act like dependency versions. The parent
should be a known quantity and not subject to environmental changes.
> Version ranges not supported for parent artifacts
> -
>
> Key: MNG-2199
> URL: https://jira.codehaus.org/browse/MNG-2199
> Project: Maven 2 & 3
> Issue Type: Bug
> Components: Inheritance and Interpolation, POM, Reactor and workspace
>Affects Versions: 2.0.3
>Reporter: Christian Schulte
> Fix For: Issues to be reviewed for 3.x
>
> Attachments: MNG-2199.patch, MNG-2199.patch
>
>
> It would be great if Maven supports version ranges when specifying parent
> artifacts in a multi-module build. Currently this does not work.
>
> artifactId
> groupId
> [2.0, 2.0.1]
>
> [INFO] Scanning for projects...
> Downloading: http://repo1.maven.org/maven2/groupId/artifactId/[2.0,
> 2.0.1]/artifactId-[2.0, 2.0.1].pom
> Additionally it would be great if this
>
> artifactId
> groupId
> [2.0, ${pom.version}]
>
> [INFO] Scanning for projects...
> Downloading: http://repo1.maven.org/maven2/groupId/artifactId/[2.0,
> ${pom.version}]/artifactId-[2.0, ${pom.version}].pom
> would also work, if the version is specified in the same pom.xml which
> defines this parent definition.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://jira.codehaus.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] (MASSEMBLY-343) add symbolic links managment
[ https://jira.codehaus.org/browse/MASSEMBLY-343?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=308864#comment-308864 ] Ahmed El-Madhoun commented on MASSEMBLY-343: By the way, I am using Maven 3, but I don't think that is an issue, would it be? > add symbolic links managment > > > Key: MASSEMBLY-343 > URL: https://jira.codehaus.org/browse/MASSEMBLY-343 > Project: Maven 2.x Assembly Plugin > Issue Type: Wish >Affects Versions: 2.2-beta-2 > Environment: linux, ubuntu >Reporter: Godet Gilles > Attachments: MASSEMBLY-343_maven-assembly-plugin_fixed.patch, > MASSEMBLY-343_maven-assembly-plugin.patch > > > i need to buid archives ( tar for example ) with symbolic links > the plugin build an archive with a file containing the destination of the > link, not the link itself > => the plugin need an option to know if deferencement of links is needed > this is just like -h option of tar > -h, --dereference > don't dump symlinks; dump the files they point to > actually, if you do an archive of /lib, for example, many file will be in > double with différent names. extract of archive will not be the exactly the > same as the source of the archive. => this is a test ! -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://jira.codehaus.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] (MASSEMBLY-343) add symbolic links managment
[ https://jira.codehaus.org/browse/MASSEMBLY-343?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=308863#comment-308863 ] Ahmed El-Madhoun commented on MASSEMBLY-343: Hi Zuhayr, Thanks for the fix, I am now able to build and test the patch. I am not seeing the symlinks respected. I am simply using assembly to archive an artifact that contains a number of symlinks, but they are all hard links. Do I need to specify any configuration in the descriptor to ensure that symlinks are kept? > add symbolic links managment > > > Key: MASSEMBLY-343 > URL: https://jira.codehaus.org/browse/MASSEMBLY-343 > Project: Maven 2.x Assembly Plugin > Issue Type: Wish >Affects Versions: 2.2-beta-2 > Environment: linux, ubuntu >Reporter: Godet Gilles > Attachments: MASSEMBLY-343_maven-assembly-plugin_fixed.patch, > MASSEMBLY-343_maven-assembly-plugin.patch > > > i need to buid archives ( tar for example ) with symbolic links > the plugin build an archive with a file containing the destination of the > link, not the link itself > => the plugin need an option to know if deferencement of links is needed > this is just like -h option of tar > -h, --dereference > don't dump symlinks; dump the files they point to > actually, if you do an archive of /lib, for example, many file will be in > double with différent names. extract of archive will not be the exactly the > same as the source of the archive. => this is a test ! -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://jira.codehaus.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] (MCHANGES-287) JIRA report add capatibility for custom locale
Bruno Marti created MCHANGES-287:
Summary: JIRA report add capatibility for custom locale
Key: MCHANGES-287
URL: https://jira.codehaus.org/browse/MCHANGES-287
Project: Maven 2.x Changes Plugin
Issue Type: Wish
Components: jira
Affects Versions: 2.8
Environment: OS XP, Maven 3.0.4
Reporter: Bruno Marti
Priority: Minor
My JIRA Query has german dates, which cannot be converted.
Getting warning: _Element "Updated". Unparseable date: "Do, 13 Sep 2012
13:52:39 +0200". Using the pattern "EE, d MMM HH:mm:ss Z"_
this is because the dates in the jira-result.xml are in german format:
_Di, 1 Nov 2011 10:47:24 +0100_ ('Di' means Thuesday)
pls, add capatibility to override the current locale 'en' for the date
conversion to 'de', like de
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://jira.codehaus.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] (MSITE-443) add a reportingManagement section
[
https://jira.codehaus.org/browse/MSITE-443?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Olivier Lamy updated MSITE-443:
---
Comment: was deleted
(was: ONLINE STORE :
+++ http://Mlink.in/6H ++
Best online store
Best quality, Best reputation , Best services
--- NHL Jersey Woman $ 40 --- NFL Jersey $ 35
--- NBA Jersey $ 34 --- MLB Jersey $ 35
--- Jordan Six Ring_m $ 36 --- Air Yeezy_m $ 45
--- T-Shirt_m $ 25 --- Jacket_m $ 36
--- Hoody_m $ 50 --- Manicure Set $ 20
--- handbag $ 37 --- ugg boot $ 43 ---
--- sunglass $ 16 --- bult $ 17 ---
+++ http://Mlink.in/6H ++)
> add a reportingManagement section
> -
>
> Key: MSITE-443
> URL: https://jira.codehaus.org/browse/MSITE-443
> Project: Maven 2.x and 3.x Site Plugin
> Issue Type: Bug
> Environment: maven-site-plugin 2.0-beta-3-SNAPSHOT
>Reporter: Indrajit Raychaudhuri
> Fix For: 3.0
>
>
> Consider the following POM:
> {code:xml}
>
>
>
>
>
> org.apache.maven.plugins
> maven-javadoc-plugin
>
> false
>
>
>
>
>
>
>
>
>
> org.apache.maven.plugins
> maven-javadoc-plugin
>
>
>
>
> {code}
> {{mvn site:site}} doesn't honor the javadoc configuration specified in the
> {{}} section.
> However, {{mvn javadoc:javadoc}} honors them.
> This is true not just for javadoc but other plugins like checkstyle as well.
> I guess, the {{}} section doesn't use the {{}}
> section at all.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://jira.codehaus.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] (MSITE-655) Finishing finding version at build.plugins.
Jin Kwon created MSITE-655:
--
Summary: Finishing finding version at build.plugins.
Key: MSITE-655
URL: https://jira.codehaus.org/browse/MSITE-655
Project: Maven 2.x and 3.x Site Plugin
Issue Type: Bug
Affects Versions: 3.1
Environment: Apache Maven 3.0.4 (r1232337; 2012-01-17 17:44:56+0900)
Maven home: C:\Programs\apache-maven-3.0.4
Java version: 1.7.0_07, vendor: Oracle Corporation
Java home: C:\Program Files\Java\jdk1.7.0_07\jre
Default locale: en_US, platform encoding: MS949
OS name: "windows 7", version: "6.1", arch: "amd64", family: "windows"
Reporter: Jin Kwon
Priority: Minor
With order/strategy explaing on
http://maven.apache.org/plugins/maven-site-plugin/maven-3.html#Version_Resolution
,
maven-site-plugin stops searching the version on build.plugins even if there is
no version specified.
With following pom,
{code:xml}
maven-javadoc-plugin
2.8.1
maven-javadoc-plugin
maven-site-plugin
maven-javadoc-plugin
{code}
maven-site-plugin seems work for maven-javadoc-plugin:2.7 not 2.8.1
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://jira.codehaus.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] (MSITE-443) add a reportingManagement section
[
https://jira.codehaus.org/browse/MSITE-443?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=308856#comment-308856
]
vvjhdsifwo commented on MSITE-443:
--
ONLINE STORE :
+++ http://Mlink.in/6H ++
Best online store
Best quality, Best reputation , Best services
--- NHL Jersey Woman $ 40 --- NFL Jersey $ 35
--- NBA Jersey $ 34 --- MLB Jersey $ 35
--- Jordan Six Ring_m $ 36 --- Air Yeezy_m $ 45
--- T-Shirt_m $ 25 --- Jacket_m $ 36
--- Hoody_m $ 50 --- Manicure Set $ 20
--- handbag $ 37 --- ugg boot $ 43 ---
--- sunglass $ 16 --- bult $ 17 ---
+++ http://Mlink.in/6H ++
> add a reportingManagement section
> -
>
> Key: MSITE-443
> URL: https://jira.codehaus.org/browse/MSITE-443
> Project: Maven 2.x and 3.x Site Plugin
> Issue Type: Bug
> Environment: maven-site-plugin 2.0-beta-3-SNAPSHOT
>Reporter: Indrajit Raychaudhuri
> Fix For: 3.0
>
>
> Consider the following POM:
> {code:xml}
>
>
>
>
>
> org.apache.maven.plugins
> maven-javadoc-plugin
>
> false
>
>
>
>
>
>
>
>
>
> org.apache.maven.plugins
> maven-javadoc-plugin
>
>
>
>
> {code}
> {{mvn site:site}} doesn't honor the javadoc configuration specified in the
> {{}} section.
> However, {{mvn javadoc:javadoc}} honors them.
> This is true not just for javadoc but other plugins like checkstyle as well.
> I guess, the {{}} section doesn't use the {{}}
> section at all.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://jira.codehaus.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] (MSITE-443) add a reportingManagement section
[
https://jira.codehaus.org/browse/MSITE-443?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=308846#comment-308846
]
Jin Kwon edited comment on MSITE-443 at 9/18/12 8:05 AM:
-
I just find that maven-site-plugin seems have some problem although works as
explained on
http://maven.apache.org/plugins/maven-site-plugin/maven-3.html#Version_Resolution.
{noformat}
maven-javadoc-plugin
2.8.1
<| must follow the lights; it doesn't.
|
|
maven-site-plugin
|
3.1
|
|
|
|
|
|
maven-javadoc-plugin <| 2.7
---|
|
|
org.apache.maven.plugins|
maven-site-plugin |
|
|
attach-descriptor |
|
attach-descriptor |
|
|
|
|
|
|
maven-javadoc-plugin ---|
{noformat}
was (Author: jinahya):
I just find that maven-site-plugin seems have some problem although works
as explained on
http://maven.apache.org/plugins/maven-site-plugin/maven-3.html#Version_Resolution.
{noformat}
maven-javadoc-plugin
2.8.1
<| must follow the lights; it doesn't.
|
|
maven-site-plugin
|
3.1
|
|
|
|
|
|
maven-javadoc-plugin <| 2.7
---|
|
|
org.apache.maven.plugins|
maven-site-plugin |
|
|
attach-descriptor |
|
attach-descriptor |
|
|
|
|
|
|
maven-javadoc-plugin ---|
{noformat}
> add a reportingManagement section
> -
>
> Key: MSITE-443
> URL: https://jira.codehaus.org/browse/MSITE-443
> Project: Maven 2.x and 3.x Site Plugin
> Issue Type: Bug
> Environment: maven-site-plugin 2.0-beta-3-SNAPSHOT
>Reporter: Indrajit Raychaudhuri
> Fix For: 3.0
>
>
> Consider the following POM:
> {code:xml}
>
>
>
>
>
> org.apache.maven.plugins
> maven-javadoc-plugin
>
> false
>
>
>
>
>
>
>
>
>
> org.apache.maven.plugins
[jira] (MSITE-443) add a reportingManagement section
[
https://jira.codehaus.org/browse/MSITE-443?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=308846#comment-308846
]
Jin Kwon edited comment on MSITE-443 at 9/18/12 8:03 AM:
-
I just find that maven-site-plugin seems have some problem although works as
explained on
http://maven.apache.org/plugins/maven-site-plugin/maven-3.html#Version_Resolution.
{noformat}
maven-javadoc-plugin
2.8.1
<| must follow the lights; it doesn't.
|
|
maven-site-plugin
|
3.1
|
|
|
|
|
|
maven-javadoc-plugin <| 2.7
---|
|
|
org.apache.maven.plugins|
maven-site-plugin |
|
|
attach-descriptor |
|
attach-descriptor |
|
|
|
|
|
|
maven-javadoc-plugin ---|
{noformat}
was (Author: jinahya):
I just find that maven-site-plugin seems have some problem although works
as explained on
http://maven.apache.org/plugins/maven-site-plugin/maven-3.html#Version_Resolution.
maven-javadoc-plugin
2.8.1
<| must follow the lights; it doesn't.
|
|
maven-site-plugin
|
3.1
|
|
|
|
|
|
maven-javadoc-plugin <| 2.7
---|
|
|
org.apache.maven.plugins|
maven-site-plugin |
|
|
attach-descriptor |
|
attach-descriptor |
|
|
|
|
|
|
maven-javadoc-plugin ---|
> add a reportingManagement section
> -
>
> Key: MSITE-443
> URL: https://jira.codehaus.org/browse/MSITE-443
> Project: Maven 2.x and 3.x Site Plugin
> Issue Type: Bug
> Environment: maven-site-plugin 2.0-beta-3-SNAPSHOT
>Reporter: Indrajit Raychaudhuri
> Fix For: 3.0
>
>
> Consider the following POM:
> {code:xml}
>
>
>
>
>
> org.apache.maven.plugins
> maven-javadoc-plugin
>
> false
>
>
>
>
>
>
>
>
>
> org
[jira] (MSITE-443) add a reportingManagement section
[
https://jira.codehaus.org/browse/MSITE-443?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=308846#comment-308846
]
Jin Kwon commented on MSITE-443:
I just find that maven-site-plugin seems have some problem although works as
explained on
http://maven.apache.org/plugins/maven-site-plugin/maven-3.html#Version_Resolution.
maven-javadoc-plugin
2.8.1
<| must follow the lights; it doesn't.
|
|
maven-site-plugin
|
3.1
|
|
|
|
|
|
maven-javadoc-plugin <| 2.7
---|
|
|
org.apache.maven.plugins|
maven-site-plugin |
|
|
attach-descriptor |
|
attach-descriptor |
|
|
|
|
|
|
maven-javadoc-plugin ---|
> add a reportingManagement section
> -
>
> Key: MSITE-443
> URL: https://jira.codehaus.org/browse/MSITE-443
> Project: Maven 2.x and 3.x Site Plugin
> Issue Type: Bug
> Environment: maven-site-plugin 2.0-beta-3-SNAPSHOT
>Reporter: Indrajit Raychaudhuri
> Fix For: 3.0
>
>
> Consider the following POM:
> {code:xml}
>
>
>
>
>
> org.apache.maven.plugins
> maven-javadoc-plugin
>
> false
>
>
>
>
>
>
>
>
>
> org.apache.maven.plugins
> maven-javadoc-plugin
>
>
>
>
> {code}
> {{mvn site:site}} doesn't honor the javadoc configuration specified in the
> {{}} section.
> However, {{mvn javadoc:javadoc}} honors them.
> This is true not just for javadoc but other plugins like checkstyle as well.
> I guess, the {{}} section doesn't use the {{}}
> section at all.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://jira.codehaus.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] (MNG-2199) Version ranges not supported for parent artifacts
[
https://jira.codehaus.org/browse/MNG-2199?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Christian Schulte updated MNG-2199:
---
Attachment: MNG-2199.patch
Updated patch.
> Version ranges not supported for parent artifacts
> -
>
> Key: MNG-2199
> URL: https://jira.codehaus.org/browse/MNG-2199
> Project: Maven 2 & 3
> Issue Type: Bug
> Components: Inheritance and Interpolation, POM, Reactor and workspace
>Affects Versions: 2.0.3
>Reporter: Christian Schulte
> Fix For: Issues to be reviewed for 3.x
>
> Attachments: MNG-2199.patch, MNG-2199.patch
>
>
> It would be great if Maven supports version ranges when specifying parent
> artifacts in a multi-module build. Currently this does not work.
>
> artifactId
> groupId
> [2.0, 2.0.1]
>
> [INFO] Scanning for projects...
> Downloading: http://repo1.maven.org/maven2/groupId/artifactId/[2.0,
> 2.0.1]/artifactId-[2.0, 2.0.1].pom
> Additionally it would be great if this
>
> artifactId
> groupId
> [2.0, ${pom.version}]
>
> [INFO] Scanning for projects...
> Downloading: http://repo1.maven.org/maven2/groupId/artifactId/[2.0,
> ${pom.version}]/artifactId-[2.0, ${pom.version}].pom
> would also work, if the version is specified in the same pom.xml which
> defines this parent definition.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://jira.codehaus.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] (MSITE-654) Appending a Slash to the Repository URL Makes Deploying to Github impossible
[
https://jira.codehaus.org/browse/MSITE-654?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=308808#comment-308808
]
Herve Boutemy commented on MSITE-654:
-
yes, I'd like myself too that we can make maven-site-plugin deploy to scm. I'm
still unsure how generic SCM publication is, since obsolete files removal is
specific, without removing subdirectories that are published by other projects
but newline inconsistencies isn't in that category: scm deploy or not,
inconsistencies should not happen. See MSITE-121
> Appending a Slash to the Repository URL Makes Deploying to Github impossible
>
>
> Key: MSITE-654
> URL: https://jira.codehaus.org/browse/MSITE-654
> Project: Maven 2.x and 3.x Site Plugin
> Issue Type: Bug
> Components: Maven 3, site:deploy
>Affects Versions: 3.1
> Environment: Maven 3.0.4
>Reporter: Rob Elliot
>
> I am attempting to deploy my site to github as described here:
> http://maven.apache.org/wagon/wagon-providers/wagon-scm/usage.html
> using the following config:
> {code:xml}
>
>
> gh-pages
> scm:git:ssh://g...@github.com/Mahoney/sandbox.git
>
>
>
>
>
> maven-site-plugin
> 3.1
>
>
> org.apache.maven.wagon
> wagon-scm
> 2.2
>
>
> org.apache.maven.scm
> maven-scm-manager-plexus
> 1.8
>
>
> org.apache.maven.scm
> maven-scm-provider-gitexe
> 1.8
>
>
> org.apache.maven.scm
> maven-scm-api
> 1.8
>
>
>
>
>
> {code}
> It fails because it tries to run the following command:
> {noformat}
> git clone ssh://g...@github.com/Mahoney/sandbox.git/
> {noformat}
> Note the trailing slash - it shouldn't be there. Remove it and the clone
> works fine.
> I have tracked this down to the following:
> {code:title=AbstractDeployMojo.java}
> public void execute()
> throws MojoExecutionException
> {
> if ( skipDeploy )
> {
> getLog().info( "maven.site.deploy.skip = true: Skipping site
> deployment" );
> return;
> }
> deployTo( new
> org.apache.maven.plugins.site.wagon.repository.Repository(
> getDeployRepositoryID(), appendSlash(
> getDeployRepositoryURL() ) ) );
> }
> /**
> * Make sure the given url ends with a slash.
> *
> * @param url a String.
> * @return if url already ends with '/' it is returned unchanged,
> * otherwise a '/' character is appended.
> */
> protected static String appendSlash( final String url )
> {
> if ( url.endsWith( "/" ) )
> {
> return url;
> }
> else
> {
> return url + "/";
> }
> }
> {code}
> The assumption that the URI to which a site is to be deployed *must* end in a
> slash renders this interaction impossible. It should surely be a matter for
> individual wagon providers to decide what processing needs to be done to the
> provided URI, rather than having the site plugin make a blanket decision with
> no knowledge of the URI formats expected.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://jira.codehaus.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] (MNG-2199) Version ranges not supported for parent artifacts
[
https://jira.codehaus.org/browse/MNG-2199?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Christian Schulte updated MNG-2199:
---
Attachment: MNG-2199.patch
Initial patch adding support for the requested feature.
> Version ranges not supported for parent artifacts
> -
>
> Key: MNG-2199
> URL: https://jira.codehaus.org/browse/MNG-2199
> Project: Maven 2 & 3
> Issue Type: Bug
> Components: Inheritance and Interpolation, POM, Reactor and workspace
>Affects Versions: 2.0.3
>Reporter: Christian Schulte
> Fix For: Issues to be reviewed for 3.x
>
> Attachments: MNG-2199.patch
>
>
> It would be great if Maven supports version ranges when specifying parent
> artifacts in a multi-module build. Currently this does not work.
>
> artifactId
> groupId
> [2.0, 2.0.1]
>
> [INFO] Scanning for projects...
> Downloading: http://repo1.maven.org/maven2/groupId/artifactId/[2.0,
> 2.0.1]/artifactId-[2.0, 2.0.1].pom
> Additionally it would be great if this
>
> artifactId
> groupId
> [2.0, ${pom.version}]
>
> [INFO] Scanning for projects...
> Downloading: http://repo1.maven.org/maven2/groupId/artifactId/[2.0,
> ${pom.version}]/artifactId-[2.0, ${pom.version}].pom
> would also work, if the version is specified in the same pom.xml which
> defines this parent definition.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://jira.codehaus.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
