Hi (Brett),
Yesterday I've copied the cargo artifacts to
repository-staging/to-ibiblio/maven (this was required because our m1 plugin
uses the "cargo" groupid).
However the sync has not happened and I can't the new 0.7 artifacts on
ibiblio (http://www.ibiblio.org/maven/cargo/jars/).
Is the sync
5 binding (Arnaud, Jason, John, Emmanuel, Lukas)
3 non-binding (Fabrizio, Stephane, Vincent S)
Cheers,
Lukas
Lukas Theussl wrote:
Hi,
Here are some more m1 plugins that I would be ready to release:
[] maven-html2xdoc-plugin-1.4
[] maven-jalopy-plugin-1.4
[] maven-javadoc-plugin-1.8
[] mave
Distribution:
http://maven.zones.apache.org/~maven/builds/branches/maven-2.0.x/m2-20060116.034500.tar.gz
Log:
http://maven.zones.apache.org/~maven/logs/branches/maven-2.0.x/m2-build-log-20060116.034500.txt
-
To unsubscribe, e-mai
Distribution:
http://maven.zones.apache.org/~maven/builds/branches/maven-2.0.x/m2-20060116.024500.tar.gz
Log:
http://maven.zones.apache.org/~maven/logs/branches/maven-2.0.x/m2-build-log-20060116.024500.txt
-
To unsubscribe, e-mai
[ http://jira.codehaus.org/browse/MRM-35?page=all ]
Maria Odea Ching updated MRM-35:
Attachment: MRM-35-maven-repository-indexer.patch
> add repository metadata indexer
> ---
>
> Key: MRM-35
> URL: http://jir
Distribution:
http://maven.zones.apache.org/~maven/builds/trunk/m2-20060116.020001.tar.gz
Log:
http://maven.zones.apache.org/~maven/logs/trunk/m2-build-log-20060116.020001.txt
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For addit
[ http://jira.codehaus.org/browse/MAVEN-1345?page=comments#action_55945 ]
Kohsuke Kawaguchi commented on MAVEN-1345:
--
dom4j 1.4 causes MPXDOC-188 (and MPXDOC-38.) (note that even though they are
marked as closed, the issue isn't fixed yet.)
> Upgra
[ http://jira.codehaus.org/browse/MPXDOC-188?page=comments#action_55942 ]
Kohsuke Kawaguchi commented on MPXDOC-188:
--
See MAVEN-1345 for a discussion about the versions of dom4j and their issues.
> relative references from xdocs/*.xml resolve incorr
[ http://jira.codehaus.org/browse/MPXDOC-188?page=all ]
Kohsuke Kawaguchi closed MPXDOC-188:
Resolution: Incomplete
It turns out dom4j is loaded from $MAVEN_HOME/lib, regardless of what the
plugin dependency specifies.
Therefore, I realized th
[ http://jira.codehaus.org/browse/MNGECLIPSE-43?page=all ]
Dmitri Maximovich closed MNGECLIPSE-43:
---
Resolution: Fixed
> M2 console should suppredd debug output if debug is disabled in preferences
> -
M2 console should suppredd debug output if debug is disabled in preferences
---
Key: MNGECLIPSE-43
URL: http://jira.codehaus.org/browse/MNGECLIPSE-43
Project: Maven 2.x Plug-in for Eclipse
Type:
relative references from xdocs/*.xml resolve incorrectly
Key: MPXDOC-188
URL: http://jira.codehaus.org/browse/MPXDOC-188
Project: maven-xdoc-plugin
Type: Bug
Versions: 1.9.2
Reporter: Kohsuke Kawag
Distribution:
http://maven.zones.apache.org/~maven/builds/branches/maven-2.0.x/m2-20060116.011501.tar.gz
Log:
http://maven.zones.apache.org/~maven/logs/branches/maven-2.0.x/m2-build-log-20060116.011501.txt
-
To unsubscribe, e-mai
[ http://jira.codehaus.org/browse/MNGECLIPSE-4?page=all ]
Dmitri Maximovich closed MNGECLIPSE-4:
--
Resolution: Fixed
> Problems with dependencies other that jar and war (ie. par, ejb3)
> --
Log:
http://maven.zones.apache.org/~maven/logs/branches/maven-2.0.x/m2-build-log-20060116.003000.txt
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
Distribution:
http://maven.zones.apache.org/~maven/builds/trunk/m2-20060116.01.tar.gz
Log:
http://maven.zones.apache.org/~maven/logs/trunk/m2-build-log-20060116.01.txt
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For addit
[ http://jira.codehaus.org/browse/MNGECLIPSE-42?page=all ]
Eugene Kuleshov closed MNGECLIPSE-42:
-
Resolution: Fixed
Fixed
> Submodules should not be added as jars to the build path
>
>
>
The test attribute is incorrectly described
---
Key: MSUREFIRE-45
URL: http://jira.codehaus.org/browse/MSUREFIRE-45
Project: Maven 2.x Surefire Plugin
Type: Improvement
Reporter: Grégory Joseph
Priority: Trivial
The
[ http://jira.codehaus.org/browse/MPSCM-67?page=all ]
Dennis Lundberg updated MPSCM-67:
-
Attachment: MPSCM-67-2.patch
> scm:prepare-release fails because project.xml has been locally modified
>
allow disabling of plugin version discovery
---
Key: MNG-1968
URL: http://jira.codehaus.org/browse/MNG-1968
Project: Maven 2
Type: Bug
Components: Plugins and Lifecycle, Artifacts and Repositories
Reporter: Brett Porte
[ http://jira.codehaus.org/browse/SCM-121?page=comments#action_55931 ]
Dennis Lundberg commented on SCM-121:
-
I tried to issue the cvs command on the command line and got back the same
error as when it was run from maven.
To see is this is a Windows iss
Done, with pleasure. /me dances for joy
It was [EMAIL PROTECTED] Obviously they alias the host name. Also took
them off the allow list (no idea how that happened) so we'll not hear
from them again, unless they resubscribe.
- Brett
Brett Porter wrote:
> I don't get it. Unless they were -allow'ed
Submodules should not be added as jars to the build path
Key: MNGECLIPSE-42
URL: http://jira.codehaus.org/browse/MNGECLIPSE-42
Project: Maven 2.x Plug-in for Eclipse
Type: Improvement
Components: Dependency
Allow configuration for whether images and css are copied to destDir
Key: MJAVADOC-50
URL: http://jira.codehaus.org/browse/MJAVADOC-50
Project: Maven 2.x Javadoc Plugin
Type: New Feature
Report
I don't get it. Unless they were -allow'ed in the past, they must be
subscribed from this address to post. But unsubscribe fails.
I'll try and figure it out, as I'd like to see the back of them (there
was also some company spam in a later message on this list).
I suspect that they are attempting
You've received instructions from us in the past several times. When you
fail to unsubscribe, you get an email how to find out.
[EMAIL PROTECTED] is *not* subscribed to any lists here. I have no
way of telling what address you are receiving them at. Email to this
address will *not* get you any fur
Dear Partner,
An open-minded company is always on the look-out for new partners
Global Identity A/S is one of Denmark’s premier IT volume distributors
selling all kinds of IT & IT related products to more that 22 different
countries all over the world. The company caters for its customers’
di
Best Regards
Global Identity A/S,
Jens Fournais
CEO
Bygstubben 3 | DK-2950 Vedbaek | Denmark
Phone: +45 45 99 31 00 | E-mail: [EMAIL PROTECTED]
MSN: [EMAIL PROTECTED]
Please visit our website at: http://www.elibitum.com
[ http://jira.codehaus.org/browse/MNG-1967?page=all ]
Brett Porter closed MNG-1967:
-
Resolution: Duplicate
> Local repository URL containing / does not work under windows
> -
>
> Key:
[ http://jira.codehaus.org/browse/MNG-1967?page=all ]
Loïc Lefèvre updated MNG-1967:
--
Attachment: bug-multiproject.zip
> Local repository URL containing / does not work under windows
> -
>
>
[ http://jira.codehaus.org/browse/MNG-1967?page=all ]
Loïc Lefèvre reopened MNG-1967:
---
By trying file:///${basedir}/thirdparty in the testcase it works fine.
However, the testcase did not relate what was my real problem. In fact, I have
a multiproject
a
[ http://jira.codehaus.org/browse/MPIR-21?page=comments#action_55925 ]
Jorg Heymans commented on MPIR-21:
--
I just updated to 2.0.2 snapshot and
maven-site-plugin-2.0-20060106.225541-3.jar , the behaviour is still there.
> no generated for archive URL
> -
[ http://jira.codehaus.org/browse/MJAVADOC-49?page=all ]
Brett Porter moved MPJAVADOC-70 to MJAVADOC-49:
---
Workflow: Maven (was: jira)
Key: MJAVADOC-49 (was: MPJAVADOC-70)
Project: Maven 2.x Javadoc Plugin (was: maven-javadoc
[ http://jira.codehaus.org/browse/MNGECLIPSE-37?page=all ]
Eugene Kuleshov updated MNGECLIPSE-37:
--
Summary: Update references to the plugin Update Site (was: Eclipse Update
Site for Plug-in not working)
> Update references to the plugin Update Sit
[ http://jira.codehaus.org/browse/MPJAVADOC-70?page=comments#action_55923 ]
Wendy Smoak commented on MPJAVADOC-70:
--
I think this belongs in MJAVADOC (Maven 2.x Javadoc Plugin).
If so, the problem with -sourcepath was corrected on January 10th in r367728
[ http://jira.codehaus.org/browse/MNGECLIPSE-41?page=all ]
Eugene Kuleshov updated MNGECLIPSE-41:
--
Version: (was: 0.0.4)
0.0.3
Fix Version: 0.0.4
> Pickup latest embedder component
>
>
>
Pickup latest embedder component
Key: MNGECLIPSE-41
URL: http://jira.codehaus.org/browse/MNGECLIPSE-41
Project: Maven 2.x Plug-in for Eclipse
Type: Task
Versions: 0.0.4
Reporter: Eugene Kuleshov
Assigned to: Eugene Kules
Embedded error: Exit code: 1 - javadoc: invalid flag: -sourcePath
-
Key: MPJAVADOC-70
URL: http://jira.codehaus.org/browse/MPJAVADOC-70
Project: maven-javadoc-plugin
Type: Bug
Environment: Windows XP j
[ http://jira.codehaus.org/browse/MPIR-21?page=comments#action_55922 ]
Brett Porter commented on MPIR-21:
--
I think this might already be fixed in the SVN version of this plugin. not yet
confirmed.
> no generated for archive URL
>
[ http://jira.codehaus.org/browse/MPIR-21?page=all ]
Brett Porter moved MSITE-76 to MPIR-21:
---
Version: (was: 2.0-beta-4)
2.0-beta-3
Key: MPIR-21 (was: MSITE-76)
Project: Maven 2.x Project Info Reports Plugin (was: Mave
[ http://jira.codehaus.org/browse/MWAR-22?page=comments#action_55921 ]
Brett Porter commented on MWAR-22:
--
Thanks for the help. Personally, I'm -1 on the patch as is.
I think we need to move to a unified solution regarding resources, that takes
into accoun
Stephane Nicoll wrote:
Once this is done, you'll be able to download
On 1/15/06, Doug Douglass <[EMAIL PROTECTED]> wrote:
Sure that works, presuming you have the source in a local project in
which you can run source:install.
But, if the source jar is in a remote repo already, I don't currentl
[ http://jira.codehaus.org/browse/MNG-1967?page=all ]
Brett Porter closed MNG-1967:
-
Assign To: Brett Porter
Resolution: Won't Fix
as I understand it, relative paths are not valid in URLs.
Try: file:///${basedir}/test
> Local repository URL cont
no generated for archive URL
--
Key: MSITE-76
URL: http://jira.codehaus.org/browse/MSITE-76
Project: Maven 2.x Site Plugin
Type: Bug
Versions: 2.0-beta-4
Reporter: Jorg Heymans
Add below mailinglist configuration t
It's not disabled (it just goes to the original m1 repo which is not
updated with your changes not deployed there).
If anyone wants to volunteer to add the rewrite rule to the source file
in maven-meeper, we can upload it.
- Brett
Vincent Massol wrote:
>
>> -Original Message-
>> From: B
It only really makes sense at the groupId level if it is being
translated. We can't do much more than that.
My hope is that everyone will use the repo manager in the next month or
so :)
- Brett
Felipe Leme wrote:
> Brett,
>
> Is the browsing going to be fixed? I mean, browsing 'by humans' is
>
Brett,
Is the browsing going to be fixed? I mean, browsing 'by humans' is
important as well...
-- Felipe
Brett Porter wrote:
It's just browsing that is disabled. Doesn't going direct to the
artifact work?
-
To unsubscri
Brett Porter wrote:
Would you mind sending some details out to that list? I am not
subscribed so I can't get to the archives.
Neither am I, actually :-(
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-ma
> -Original Message-
> From: Brett Porter [mailto:[EMAIL PROTECTED]
> Sent: dimanche 15 janvier 2006 18:54
> To: Maven Developers List
> Subject: Re: Cargo artifacts not served by the m1 repo on ibiblio
>
> It's just browsing that is disabled. Doesn't going direct to the
> artifact work?
Once this is done, you'll be able to download
On 1/15/06, Doug Douglass <[EMAIL PROTECTED]> wrote:
> Sure that works, presuming you have the source in a local project in
> which you can run source:install.
>
> But, if the source jar is in a remote repo already, I don't currently
> see a way to dow
I'm creating a patch for MNG-1677 and need to know what the policy is
for linking between sites for different parts of Maven.
In this case I need to create a link from maven-components (maven-model)
to maven-scm. Should I use an absolute or a relative link?
http://maven.apache.org/scm/scm-u
The admins were (I had to enable .htaccess via the helpdesk).
Would you mind sending some details out to that list? I am not
subscribed so I can't get to the archives.
- Brett
Felipe Leme wrote:
> BTW, when these rewrite rules were created, were the ibiblio admins been
> notified on the changes?
It's just browsing that is disabled. Doesn't going direct to the
artifact work?
- Brett
Vincent Massol wrote:
> Hi (Brett),
>
> The Cargo 0.7 artifacts are correctly served by the m2 repo on ibiblio
> (http://www.ibiblio.org/maven2/org/codehaus/cargo/). However the URL
> rewriting rules for maki
Wendy Smoak wrote:
> Not to mention that it's an interface, so instantiating it would be
> pretty difficult.
Right, though a converter would know to instantiate a useful
implementation using an artifactFactory.
> No problem... though it does seem like duplication, I think because
> DefaultArtifac
BTW, when these rewrite rules were created, were the ibiblio admins been
notified on the changes?
I'm asking because we mirrors ibiblio at work and the guy responsible
for the job wasn't aware of the change, even though he is subscribed to
the ibiblio-mirrors list
(http://lists.ibiblio.org/ma
[ http://jira.codehaus.org/browse/MJAR-5?page=comments#action_55913 ]
Lukas Theussl commented on MJAR-5:
--
See MPJAR-51 and MPJAR-7 for related discussions in the m1 plugin.
> no Implementation-Vendor-Id in META-INF/MANIFEST.MF
>
[ http://jira.codehaus.org/browse/MJAR-3?page=all ]
Mike Perham closed MJAR-3:
--
Assign To: Mike Perham
Resolution: Duplicate
MJAR-10
> LICENSE.txt no longer saved in META-INF
> ---
>
> Key: MJAR-3
>
[ http://jira.codehaus.org/browse/MJAR-5?page=comments#action_55907 ]
Mike Perham commented on MJAR-5:
Here's an example I found from the Sun spec. What data from the POM should be
used though? I can't think any elements which fit this requirement. Maybe
Invalid m2 pom for joda-time-hibernate-0.8
--
Key: MEV-302
URL: http://jira.codehaus.org/browse/MEV-302
Project: Maven Evangelism
Type: Bug
Components: Invalid POM
Reporter: Grégory Joseph
Attachments: pom.patch
The
[ http://jira.codehaus.org/browse/MEV-302?page=all ]
Grégory Joseph updated MEV-302:
---
Attachment: pom.patch
> Invalid m2 pom for joda-time-hibernate-0.8
> --
>
> Key: MEV-302
> URL: http://jira.code
relocate xerces:xerces or xerces:xercesImpl
---
Key: MEV-301
URL: http://jira.codehaus.org/browse/MEV-301
Project: Maven Evangelism
Type: Bug
Reporter: fabrizio giustina
At the moment xerces jars are distributed both wit
Local repository URL containing / does not work under windows
-
Key: MNG-1967
URL: http://jira.codehaus.org/browse/MNG-1967
Project: Maven 2
Type: Bug
Components: Artifacts and Repositories
Versions
[ http://jira.codehaus.org/browse/MWAR-22?page=comments#action_55905 ]
Cameron Braid commented on MWAR-22:
---
related to http://www.mail-archive.com/users@maven.apache.org/msg10554.html
thread
> patch to allow extra webapp and webapp/WEB-INF/classes files t
patch to allow extra webapp and webapp/WEB-INF/classes files to be specified
that override existing files
-
Key: MWAR-22
URL: http://jira.codehaus.org/browse/MWAR-22
Proj
Stephane Nicoll wrote:
On 1/14/06, Doug Douglass <[EMAIL PROTECTED]> wrote:
The only problem I see is that the eclipse plugin does not install the
sources in the local repository, thus making it appear that it does not
work. Perhaps this is the reason it's not working for you Arnaud?
What
javacc version 4.0
--
Key: MAVENUPLOAD-683
URL: http://jira.codehaus.org/browse/MAVENUPLOAD-683
Project: maven-upload-requests
Type: Task
Reporter: Greg Kick
I am requesting that version 4.0 of javacc be added to the repository. Please
see th
Distribution:
http://maven.zones.apache.org/~maven/builds/branches/maven-2.0.x/m2-20060115.131501.tar.gz
Log:
http://maven.zones.apache.org/~maven/logs/branches/maven-2.0.x/m2-build-log-20060115.131501.txt
-
To unsubscribe, e-mai
Distribution:
http://maven.zones.apache.org/~maven/builds/trunk/m2-20060115.130001.tar.gz
Log:
http://maven.zones.apache.org/~maven/logs/trunk/m2-build-log-20060115.130001.txt
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For addit
Distribution:
http://maven.zones.apache.org/~maven/builds/branches/maven-2.0.x/m2-20060115.114500.tar.gz
Log:
http://maven.zones.apache.org/~maven/logs/branches/maven-2.0.x/m2-build-log-20060115.114500.txt
-
To unsubscribe, e-mai
Distribution:
http://maven.zones.apache.org/~maven/builds/trunk/m2-20060115.113001.tar.gz
Log:
http://maven.zones.apache.org/~maven/logs/trunk/m2-build-log-20060115.113001.txt
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For addit
Quotes in project produce 'illegal package name' error
-
Key: MJAVADOC-48
URL: http://jira.codehaus.org/browse/MJAVADOC-48
Project: Maven 2.x Javadoc Plugin
Type: Bug
Reporter: Kenney Westerhof
Pri
[ http://jira.codehaus.org/browse/MAVEN-1740?page=comments#action_55901 ]
Kohsuke Kawaguchi commented on MAVEN-1740:
--
This currently prevents Maven 1.1 beta2 users from accessing the java.net maven
repository.
See WAGONHTTP-5 for another blocker.
>
[ http://jira.codehaus.org/browse/MAVEN-1740?page=comments#action_55900 ]
Kohsuke Kawaguchi commented on MAVEN-1740:
--
Simply changing the problematic line to:
if ( repository.getProtocol().equals( "http" ) ||
repository.getProtocol().equals( "https
Hi (Brett),
The Cargo 0.7 artifacts are correctly served by the m2 repo on ibiblio
(http://www.ibiblio.org/maven2/org/codehaus/cargo/). However the URL
rewriting rules for making the m2 repo a m1 repo do not seem to work.
I'm not sure what the URL should be but I've tried:
http://www.ibiblio.org
https repositories are not supported
Key: MAVEN-1740
URL: http://jira.codehaus.org/browse/MAVEN-1740
Project: Maven
Type: Bug
Components: core
Versions: 1.1-beta-2
Environment: Windows XP
Reporter: Kohsuke Kawagu
75 matches
Mail list logo
