I don't believe this to be the right solution (we should not need to
modify the m1 or m2 plugins).
- Brett
Nicolas De Loof wrote:
I've found it myself in maven SVN :
(maven/components/trunk/maven-meeper/src/bin/ibiblio-htaccess)
The current rewrite rule converts
group/java-sources/artifact
Thanks a lot Emmanuel
Emmanuel Venisse a écrit :
http://jira.codehaus.org/browse/MPA-72
Emmanuel
Nicolas De Loof a écrit :
I can't select "Maven Project Administration" in Jira "create bug"
page :
http://jira.codehaus.org/secure/CreateIssue!default.jspa
BUT I can search for issues on thi
http://jira.codehaus.org/browse/MPA-72
Emmanuel
Nicolas De Loof a écrit :
I can't select "Maven Project Administration" in Jira "create bug" page :
http://jira.codehaus.org/secure/CreateIssue!default.jspa
BUT I can search for issues on this project... Is this a JIRA
configuration bug ? Would
I can't select "Maven Project Administration" in Jira "create bug" page :
http://jira.codehaus.org/secure/CreateIssue!default.jspa
BUT I can search for issues on this project... Is this a JIRA
configuration bug ? Would I create a Jira Issue about Jira config ;-)
Nico.
Brett Porter a écrit :
Please put it in JIRA under the project MPA (Maven Project
Administration) - thanks.
Nicolas De Loof wrote:
I've found it myself in maven SVN :
(maven/components/trunk/maven-meeper/src/bin/ibiblio-htaccess)
The current rewrite rule converts
group/java-sources/artifact-xyz-sources.jar
to
gro
I've found it myself in maven SVN :
(maven/components/trunk/maven-meeper/src/bin/ibiblio-htaccess)
The current rewrite rule converts
group/java-sources/artifact-xyz-sources.jar
to
group/artifact/artifact-xyz-java-sources.jar
So I can see three options :
1. Add a new Rule for "java-sources"
Hello guys,
From a previous post I know Maven1 repo is a redirect to maven2
repository content, with path transcripted to match maven2 hierarchy.
commons-collection (as an example) has sources jar in maven2 repo
(http://www.ibiblio.org/maven2/commons-collections/commons-collections/3.1/commo
