They need a ssh accessible server with their repo and add the maven
public key (which is available somewhere, I can send it) so we can
connect and grab everything.
On 1/16/06, Felipe Leme <[EMAIL PROTECTED]> wrote:
> Brett/Carlos (and others :-),
>
> Is there a policy where a 3rd party open source
[ http://jira.codehaus.org/browse/MNG-1923?page=all ]
Milos Kleint closed MNG-1923:
-
Resolution: Fixed
Fix Version: 2.0.2
patch applied by brett.
> please add reference to netbeans maven2 integration from the the maven2 site
>
[ http://jira.codehaus.org/browse/MPECLIPSE-84?page=all ]
Felipe Leme closed MPECLIPSE-84:
Resolution: Fixed
Fix Version: 1.11
Fixed, by creating the maven.eclipse.project.name, which is more generic than
simply adding a prefix (see my previou
Brett/Carlos (and others :-),
Is there a policy where a 3rd party open source project could
automaticaly synchronize their jars into ibiblio (without having to
submit a MAVENUPLOAD request)? The interested party in this case is the
emma project:
https://sourceforge.net/forum/message.php?msg_
Distribution:
http://maven.zones.apache.org/~maven/builds/branches/maven-2.0.x/m2-20060117.031501.tar.gz
Log:
http://maven.zones.apache.org/~maven/logs/branches/maven-2.0.x/m2-build-log-20060117.031501.txt
-
To unsubscribe, e-mai
[ http://jira.codehaus.org/browse/MNGECLIPSE-39?page=comments#action_56058
]
Eugene Kuleshov commented on MNGECLIPSE-39:
---
Archimedes, what do you mean "in the Project"?
Actually I was thinking to use some extension of the WTP structured editor (th
[ http://jira.codehaus.org/browse/MRM-35?page=comments#action_56057 ]
Edwin Punzalan commented on MRM-35:
---
Both patches applied. Thanks.
> add repository metadata indexer
> ---
>
> Key: MRM-35
> URL: http://jir
[ http://jira.codehaus.org/browse/MNGECLIPSE-39?page=comments#action_56056
]
Archimedes Trajano commented on MNGECLIPSE-39:
--
Rather than an all out form, why not just a property sheet in the Project? It
might be easier to build and probably mo
Distribution:
http://maven.zones.apache.org/~maven/builds/branches/maven-2.0.x/m2-20060117.024501.tar.gz
Log:
http://maven.zones.apache.org/~maven/logs/branches/maven-2.0.x/m2-build-log-20060117.024501.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/branches/maven-2.0.x/m2-20060117.021500.tar.gz
Log:
http://maven.zones.apache.org/~maven/logs/branches/maven-2.0.x/m2-build-log-20060117.021500.txt
-
To unsubscribe, e-mai
[ http://jira.codehaus.org/browse/MAVENUPLOAD-683?page=all ]
Carlos Sanchez closed MAVENUPLOAD-683:
--
Assign To: Carlos Sanchez
Resolution: Fixed
> javacc version 4.0
> --
>
> Key: MAVENUPLOAD-683
> URL: ht
[ http://jira.codehaus.org/browse/MAVENUPLOAD-678?page=all ]
Carlos Sanchez closed MAVENUPLOAD-678:
--
Assign To: Carlos Sanchez
Resolution: Fixed
> Please, upload JGroups 2.2.9.1 to the ibiblio repository.
>
[ http://jira.codehaus.org/browse/MEV-305?page=all ]
Carlos Sanchez moved MAVENUPLOAD-672 to MEV-305:
Bundle URL: (was:
http://www.ibiblio.org/maven2/cactus/cactus/13-1.7/cactus-13-1.7.pom)
Project URL: (was: http://jakar
Distribution:
http://maven.zones.apache.org/~maven/builds/trunk/m2-20060117.020001.tar.gz
Log:
http://maven.zones.apache.org/~maven/logs/trunk/m2-build-log-20060117.020001.txt
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For addit
[
http://jira.codehaus.org/browse/MAVENUPLOAD-683?page=comments#action_56049 ]
Greg Kick commented on MAVENUPLOAD-683:
---
fixed it. sorry about that.
> javacc version 4.0
> --
>
> Key: MAVENUPLOAD-683
> URL: http://jir
[ http://jira.codehaus.org/browse/MWAR-22?page=comments#action_56047 ]
Brett Porter commented on MWAR-22:
--
I tihnk we might need to bring the discussion up on dev@maven.apache.org and
work through it from beginning to end.
Review MRESOURCES-8 and related i
[ http://jira.codehaus.org/browse/SCM-132?page=comments#action_56046 ]
Emmanuel Venisse commented on SCM-132:
--
It isn't possible actually to use extssh protocol because cvs command line
doesn't know this non-standard protocol. I think we'll can use it w
Log:
http://maven.zones.apache.org/~maven/logs/branches/maven-2.0.x/m2-build-log-20060117.014501.txt
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
Log:
http://maven.zones.apache.org/~continuum/logs/continuum-build-log-20060117.013001.txt
[ http://jira.codehaus.org/browse/SCM-121?page=comments#action_56045 ]
Emmanuel Venisse commented on SCM-121:
--
All tests runs fine for me. I use win XP and cygwin cvs (1.11.17) under windows.
> Intermittent CVS test failures
> --
[ http://jira.codehaus.org/browse/MAVENUPLOAD-654?page=all ]
Carlos Sanchez closed MAVENUPLOAD-654:
--
Assign To: Carlos Sanchez
Resolution: Incomplete
> please upload retrotranslator jars for 0.9.5
>
[
http://jira.codehaus.org/browse/MAVENUPLOAD-678?page=comments#action_56044 ]
Carlos Sanchez commented on MAVENUPLOAD-678:
unable to download
> Please, upload JGroups 2.2.9.1 to the ibiblio repository.
>
[ http://jira.codehaus.org/browse/MAVENUPLOAD-685?page=all ]
Carlos Sanchez closed MAVENUPLOAD-685:
--
Assign To: Carlos Sanchez
Resolution: Fixed
Next time please paste the urls in the issue
> Upload request for SLF4J 1.0RC5 and NLOG4J 1.
[ http://jira.codehaus.org/browse/MEV-304?page=all ]
Carlos Sanchez moved MAVENUPLOAD-679 to MEV-304:
Group ID: jtds
Bundle URL: (was:
http://www.ibiblio.org/maven2/net/sourceforge/jtds/jtds/1.2/)
Project URL:
[ http://jira.codehaus.org/browse/MAVENUPLOAD-684?page=all ]
Carlos Sanchez closed MAVENUPLOAD-684:
--
Assign To: Carlos Sanchez
Resolution: Fixed
> Upload Click 0.18 bundles
> -
>
> Key: MAVENUPLOAD-684
>
[
http://jira.codehaus.org/browse/MAVENUPLOAD-683?page=comments#action_56042 ]
Carlos Sanchez commented on MAVENUPLOAD-683:
groupid has to be net.java.dev.javacc
> javacc version 4.0
> --
>
> Key: MAVENUPLOAD-683
>
[ http://jira.codehaus.org/browse/MAVENUPLOAD-682?page=all ]
Carlos Sanchez closed MAVENUPLOAD-682:
--
Assign To: Carlos Sanchez
Resolution: Fixed
> ARM 4.0 Java Language Binding
> -
>
> Key: MAVENUPLOAD-
[ http://jira.codehaus.org/browse/MAVENUPLOAD-681?page=all ]
Carlos Sanchez closed MAVENUPLOAD-681:
--
Assign To: Carlos Sanchez
Resolution: Fixed
next time, please use only one issue
> OSGi R4 compendium
> --
>
> K
[ http://jira.codehaus.org/browse/MAVENUPLOAD-680?page=all ]
Carlos Sanchez closed MAVENUPLOAD-680:
--
Assign To: Carlos Sanchez
Resolution: Fixed
> OSGi R4 core
>
>
> Key: MAVENUPLOAD-680
> URL: http://jira.co
[ http://jira.codehaus.org/browse/MEV-303?page=all ]
Carlos Sanchez updated MEV-303:
---
Group ID: tapestry (was: t)
> POM for Tapestry 4.0
>
>
> Key: MEV-303
> URL: http://jira.codehaus.org/browse/MEV-303
> Projec
[ http://jira.codehaus.org/browse/MEV-303?page=all ]
Carlos Sanchez moved MAVENUPLOAD-677 to MEV-303:
Group ID: t
Bundle URL: (was: http://howardlewisship.com/maven/tapestry-4.0.pom)
Project URL: (was: http://ja
[ http://jira.codehaus.org/browse/MAVENUPLOAD-676?page=all ]
Carlos Sanchez closed MAVENUPLOAD-676:
--
Assign To: Carlos Sanchez
Resolution: Fixed
> Please Upload Registry J2SE
> ---
>
> Key: MAVENUPLOAD-676
What's wrong with making them an integration test?
Eric
On 1/16/06, dan tran <[EMAIL PROTECTED]> wrote:
>
> Folks, The native-plugin redefine build lifecycle as
>
>
>
> org.apache.maven.lifecycle.mapping.LifecycleMapping
>
> dll
>
>
> org.apache.maven.lifecycle.mapping.DefaultLifecycleMa
Log:
http://maven.zones.apache.org/~maven/logs/branches/maven-2.0.x/m2-build-log-20060117.011502.txt
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
When you say "anonymous" and "developer", could those be "pserver" and
"ext" instead?
Yes, that's what I meant.
-Lukas
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
Log:
http://maven.zones.apache.org/~maven/logs/branches/maven-2.0.x/m2-build-log-20060117.003001.txt
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
Dennis Lundberg wrote:
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://ma
Distribution:
http://maven.zones.apache.org/~maven/builds/trunk/m2-20060117.00.tar.gz
Log:
http://maven.zones.apache.org/~maven/logs/trunk/m2-build-log-20060117.00.txt
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For addit
Interesting!
This helps narrow down where to look. I'm now convinced that the problem
lies in maven-scm. I found a couple of issues in there but have not
found the solution for this one yet.
When you say "anonymous" and "developer", could those be "pserver" and
"ext" instead?
--
Dennis Lun
[ http://jira.codehaus.org/browse/MAVENUPLOAD-675?page=all ]
Carlos Sanchez closed MAVENUPLOAD-675:
--
Assign To: Carlos Sanchez
Resolution: Fixed
> Please Upload Registry CDC
> --
>
> Key: MAVENUPLOAD-675
>
Folks, The native-plugin redefine build lifecycle as
org.apache.maven.lifecycle.mapping.LifecycleMapping
dll
org.apache.maven.lifecycle.mapping.DefaultLifecycleMapping
org.codehaus.mojo:native-maven-plugin:compile
org.codehaus.mojo:native-maven-plugin:link
[ http://jira.codehaus.org/browse/MAVEN-1722?page=all ]
Lukas Theussl closed MAVEN-1722:
Resolution: Fixed
Fix Version: 1.1-beta-3
Patch applied. Thanks!
> Documentation fixes to the User's guide
> ---
>
>
Distribution:
http://maven.zones.apache.org/~maven/builds/branches/maven-2.0.x/m2-20060116.224500.tar.gz
Log:
http://maven.zones.apache.org/~maven/logs/branches/maven-2.0.x/m2-build-log-20060116.224500.txt
-
To unsubscribe, e-mai
[ http://jira.codehaus.org/browse/SCM-133?page=comments#action_56035 ]
Trygve Laugstol commented on SCM-133:
-
IIRC this was to minimize the info to the provider to exactly what it needed.
There's a lot of code that's shared between and hidden from the pr
Wrong source url on website
---
Key: MJAVADOC-51
URL: http://jira.codehaus.org/browse/MJAVADOC-51
Project: Maven 2.x Javadoc Plugin
Type: Bug
Environment: Web browser
Reporter: Keith E Campbell
The website
http://maven.apache.org/plug
Dennis,
I'm on Linux, latest snapshot plugins from svn and maven-scm 1.0-beta-2.
In short: I can reproduce the problem, 'maven scm:status' gives me the
same error that you got (password is required). When I do a 'cvs login'
manually before, the build succeeds, but I don't get any output.
One
[ http://jira.codehaus.org/browse/MAVENUPLOAD-674?page=all ]
Carlos Sanchez closed MAVENUPLOAD-674:
--
Assign To: Carlos Sanchez
Resolution: Fixed
done
Contributor URL should only be used if you're a contributor
> Enhydra XMLC Compiler & An
[ http://jira.codehaus.org/browse/MPSCM-67?page=all ]
Lukas Theussl closed MPSCM-67:
--
Resolution: Fixed
Fix Version: 1.6
Patch applied. Thanks!
> scm:prepare-release fails because project.xml has been locally modified
> --
[ http://jira.codehaus.org/browse/MAVENUPLOAD-645?page=all ]
Carlos Sanchez closed MAVENUPLOAD-645:
--
Resolution: Fixed
overwritten
> Jini Service Archetype version 2.0
> --
>
> Key: MAVENUPLOAD-645
>
[ http://jira.codehaus.org/browse/MAVENUPLOAD-673?page=all ]
Carlos Sanchez closed MAVENUPLOAD-673:
--
Assign To: Carlos Sanchez
Resolution: Fixed
> Weblets 0.1
> ---
>
> Key: MAVENUPLOAD-673
> URL: http://jira.code
[ http://jira.codehaus.org/browse/MRELEASE-72?page=all ]
Emmanuel Venisse closed MRELEASE-72:
Assign To: Emmanuel Venisse
Resolution: Fixed
Fixed in Maven-SCM
> maven-release-plugin doesn't pass username to maven-scm-provider-cvs
> ---
[ http://jira.codehaus.org/browse/MRELEASE-65?page=all ]
Emmanuel Venisse closed MRELEASE-65:
Resolution: Duplicate
Duplicate with MRELEASE-72
> problem with scm url without username
> -
>
> Key: MRE
Continuum use checkout, update and changelog
release plugin use checkout, status, tag and checkin
scm plugin use all commands (http://maven.apache.org/scm/plugins/index.html)
Emmanuel
Mike Perham a écrit :
Not that I know of. Different clients use different parts. For instance, the
release p
[ http://jira.codehaus.org/browse/SCM-132?page=all ]
Lukas Theussl updated SCM-132:
--
Component: maven-plugin
> extssh connection method not shown
> --
>
> Key: SCM-132
> URL: http://jira.codehaus.org/browse/
Not that I know of. Different clients use different parts. For instance, the
release plugin uses checkin whereas continuum does not. I believe we have an
scm plugin which can exercise most of the commands. Can someone link to some
documentation for it?
mike
-Original Message-
From:
Hi Lukas
MPSCM-67 is a different matter. The new patch for that issue was
uploaded because the first patch used absolute paths (in the svn diff
itself, not in maven code). That issue is solved by the patch there.
This problem, on the other hand, I haven't solved yet. I figured that I
would u
Dennis,
Have you figured out what was going on here? Does the second patch that
you attached to MPSCM-67 fix this?
Cheers,
Lukas
Dennis Lundberg wrote:
Hi all
I'm beginning to get grey hairs now...
I just finished the patch for MPSCM-67 which solved a problem I had.
When developing the p
[ http://jira.codehaus.org/browse/MAVEN-1740?page=all ]
Lukas Theussl closed MAVEN-1740:
Resolution: Fixed
Fix Version: 1.1-beta-3
Fixed. Thanks!
> https repositories are not supported
>
>
> Key: M
Thanks!
Maven
is now the happy app with one more scm provider.
Now, how do I make continuum pick up the
new provider?
T
-Original Message-From: dan tran
[mailto:[EMAIL PROTECTED]Sent: 15. januar 2006 18:38To:
scm-dev@maven.apache.orgSubject: Re: How to add new
SCM
yo
[ http://jira.codehaus.org/browse/MPDASHBOARD-35?page=all ]
Lukas Theussl closed MPDASHBOARD-35:
Resolution: Fixed
Fix Version: 1.9
Patch applied. Thanks!
> Do not count changelog filesets
> ---
>
> Key
http://repo1.maven.org/maven/cargo/jars/cargo-core-uberjar-0.7.jar
works for me.
Syncing plugins now.
- Brett
Vincent Massol wrote:
>
>> -Original Message-
>> From: Brett Porter [mailto:[EMAIL PROTECTED]
>> Sent: lundi 16 janvier 2006 18:20
>> To: Maven Developers List
>> Subject: Re: S
[ http://jira.codehaus.org/browse/MNGECLIPSE-30?page=comments#action_56011
]
Federico Sauter commented on MNGECLIPSE-30:
---
Using JDK 5 on the testproject gives an error with a different version number:
"Unable to download the artifact from any repo
Distribution:
http://maven.zones.apache.org/~maven/builds/branches/maven-2.0.x/m2-20060116.171501.tar.gz
Log:
http://maven.zones.apache.org/~maven/logs/branches/maven-2.0.x/m2-build-log-20060116.171501.txt
-
To unsubscribe, e-mai
> -Original Message-
> From: Brett Porter [mailto:[EMAIL PROTECTED]
> Sent: lundi 16 janvier 2006 18:20
> To: Maven Developers List
> Subject: Re: Syncing repository-staging/maven to ibiblio?
>
> As I said in my previous mail, yes, its turned off. The only thing that
> will harm is plugi
[ http://jira.codehaus.org/browse/MNGECLIPSE-30?page=comments#action_56010
]
Federico Sauter commented on MNGECLIPSE-30:
---
I have attached a small project that intents to reproduce at least some of the
problems I described. I hope this will give yo
As I said in my previous mail, yes, its turned off. The only thing that
will harm is plugins. Artifacts in the "m1" repo are served out of m2
anyway, so there is no point including them in the m1 repo, but plugins
are not converted.
Is it only a plugin that is the issue? I will sync it across manu
[ http://jira.codehaus.org/browse/MRELEASE-25?page=all ]
Jason van Zyl updated MRELEASE-25:
--
Fix Version: 2.0-beta-5
> "next dev" version of pom gets release info
> ---
>
> Key: MRELEASE-25
> URL
[ http://jira.codehaus.org/browse/MNGECLIPSE-30?page=all ]
Federico Sauter updated MNGECLIPSE-30:
--
Attachment: mvn_test-output.txt
plugin-test.zip
> Maven plugin keeps looking for non-existent apacheds-*-2.4.1 dependency
> --
[ http://jira.codehaus.org/browse/MRELEASE-20?page=all ]
Jason van Zyl updated MRELEASE-20:
--
Fix Version: 2.0-beta-5
> remove release.properties after successful release:perform
> --
>
> K
[ http://jira.codehaus.org/browse/MRELEASE-3?page=all ]
Jason van Zyl updated MRELEASE-3:
-
Fix Version: 2.0-beta-5
> release:prepare should not require multimodule artifacts to be in the local
> repository
> -
[ http://jira.codehaus.org/browse/MRELEASE-66?page=all ]
Jason van Zyl updated MRELEASE-66:
--
Fix Version: 2.0-beta-5
> Source and Javadoc bundles should be optional
> -
>
> Key: MRELEASE-66
>
[ http://jira.codehaus.org/browse/MRELEASE-44?page=all ]
Jason van Zyl updated MRELEASE-44:
--
Fix Version: 2.0-beta-5
> release:perform doesn't work at all without release.properties
> --
>
>
[ http://jira.codehaus.org/browse/MRELEASE-4?page=all ]
Jason van Zyl updated MRELEASE-4:
-
Fix Version: 2.0-beta-5
> release plugin should ignore pom.xml from status check
> --
>
> Key: MRELEAS
[ http://jira.codehaus.org/browse/MRELEASE-60?page=all ]
Jason van Zyl updated MRELEASE-60:
--
Fix Version: 2.0-beta-5
> release plugin must rewrite scm connection (for svn projects) url in tagged
> pom or set scm tag in tagged pom for other scm
> --
[ http://jira.codehaus.org/browse/MRELEASE-48?page=all ]
Jason van Zyl updated MRELEASE-48:
--
Fix Version: 2.0-beta-5
> release:prepare fails when release.properties already exists
>
>
>
[ http://jira.codehaus.org/browse/MRELEASE-31?page=all ]
Jason van Zyl updated MRELEASE-31:
--
Fix Version: 2.0-beta-5
> Dependency management versions should only be updated if they are SNAPSHOTs
>
[ http://jira.codehaus.org/browse/MRELEASE-24?page=all ]
Jason van Zyl updated MRELEASE-24:
--
Fix Version: 2.0-beta-5
> release.properties should be removed between (failed) release runs
> -
[ http://jira.codehaus.org/browse/MRELEASE-35?page=all ]
Jason van Zyl updated MRELEASE-35:
--
Fix Version: 2.0-beta-5
> release plugin doesn't tag correctly with svn+ssh when remote and local
> username don't match
>
[ http://jira.codehaus.org/browse/MNG-1898?page=all ]
Joakim Erdfelt updated MNG-1898:
Attachment: MNG-1898-coreit.tar.bz2
> Plugin classpath broken from 2.0 to 2.0.1
> -
>
> Key: MNG-1898
> URL:
Distribution:
http://maven.zones.apache.org/~maven/builds/trunk/m2-20060116.170001.tar.gz
Log:
http://maven.zones.apache.org/~maven/logs/trunk/m2-build-log-20060116.170001.txt
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For addit
[ http://jira.codehaus.org/browse/MRELEASE-69?page=all ]
Jason van Zyl closed MRELEASE-69:
-
Resolution: Fixed
We now walk through the reactor of project projects and check them all for
external dependencies that may be snapshots and stop the releas
[ http://jira.codehaus.org/browse/MSUREFIRE-40?page=comments#action_56006 ]
Jesse Kuhnert commented on MSUREFIRE-40:
I accidently addressed this in the top level issue comments, but my first
thoughts were that it should probably be ok to add specific
[ http://jira.codehaus.org/browse/MRELEASE-69?page=all ]
Jason van Zyl updated MRELEASE-69:
--
Summary: User should be warned up-front if there external snapshot
dependencies in the build (was: User should be warned up-front if anything is
incorrect ins
[ http://jira.codehaus.org/browse/MSUREFIRE-23?page=comments#action_56005 ]
Jesse Kuhnert commented on MSUREFIRE-23:
Gunnar,
In regard to the 3 vs 2 suite assertion, it really should be 3 suites found. It
could be an indicator that the testng report
[ http://jira.codehaus.org/browse/MSUREFIRE-23?page=all ]
Jesse Kuhnert updated MSUREFIRE-23:
---
Attachment: surefire-report-maven-plugin-patch.txt
surefire-patch.txt
> Support TestNG
> --
>
> Key: MSUREFIRE-23
>
extssh connection method not shown
--
Key: MPSCM-72
URL: http://jira.codehaus.org/browse/MPSCM-72
Project: maven-scm-plugin
Type: Bug
Environment: Windows 2000; Java 1.4 JDK, Maven 2.01 maven-scm-plugin
1.0-alpha-2
Reporter: Tod
[ http://jira.codehaus.org/browse/MNGECLIPSE-44?page=all ]
Eugene Kuleshov closed MNGECLIPSE-44:
-
Resolution: Duplicate
> XML namespace info should not be descarted
> --
>
> Key: MNGECLIPSE-44
>
[ http://jira.codehaus.org/browse/MNGECLIPSE-44?page=all ]
Eugene Kuleshov updated MNGECLIPSE-44:
--
Component: (was: Wizards)
> XML namespace info should not be descarted
> --
>
> Key: MNGECLIPSE-4
[ http://jira.codehaus.org/browse/MNGECLIPSE-21?page=comments#action_56001
]
Eugene Kuleshov commented on MNGECLIPSE-21:
---
Michal, and why do you think there are duplicated classes? Unles those classes
blong to completely independent jars and loade
[ http://jira.codehaus.org/browse/MNGECLIPSE-22?page=comments#action_56000
]
Eugene Kuleshov commented on MNGECLIPSE-22:
---
I completely forgot about JavaLaunchDelegate. It seems the only way is to
maintain two separate code streams for the plugin.
[ http://jira.codehaus.org/browse/MWAR-12?page=comments#action_55999 ]
Cameron Braid commented on MWAR-12:
---
related to http://jira.codehaus.org/browse/MWAR-22
I think that adding a prepare-package phase is the best way to go.
This will allow 2 things :
1
Improve SVN directory structure
---
Key: DOXIA-46
URL: http://jira.codehaus.org/browse/DOXIA-46
Project: doxia
Type: Improvement
Reporter: Grzegorz Slowikowski
Priority: Trivial
1.
I think that doxia-module-twiki should be moved
[ http://jira.codehaus.org/browse/MWAR-22?page=comments#action_55997 ]
Cameron Braid commented on MWAR-22:
---
Ok.. I am all for that.
Any ideas on a timeline ?
Is there anything that I can do to help ?
> patch to allow extra webapp and webapp/WEB-INF/class
I'm looking at a the support of the proxies in the site:deploy goal.
I discovered a few strange things, and I would like to have some explanation
on the proxy support philosophy.
In maven settings, we have the possibility to define multiple proxies, with
their type (http, socks, etc). The Defaul
Do not count changelog filesets
---
Key: MPDASHBOARD-35
URL: http://jira.codehaus.org/browse/MPDASHBOARD-35
Project: maven-dashboard-plugin
Type: Bug
Versions: 1.9
Reporter: Christoph Jerolimov
Attachments: dashboard-fix-chan
XML namespace info should not be descarted
--
Key: MNGECLIPSE-44
URL: http://jira.codehaus.org/browse/MNGECLIPSE-44
Project: Maven 2.x Plug-in for Eclipse
Type: Bug
Components: Wizards
Versions: 0.0.3
Environment:
[ http://jira.codehaus.org/browse/MWAR-20?page=comments#action_55994 ]
David Boden commented on MWAR-20:
-
The problem is that the relative addressing doesn' t work. If you start the
path with ${basedir}/ then it works fine. This is what I've used as a
worka
Mojo not getting configuration from pom in integration-test phase
-
Key: MNG-1969
URL: http://jira.codehaus.org/browse/MNG-1969
Project: Maven 2
Type: Bug
Components: integration tests
Versions:
[ http://jira.codehaus.org/browse/MASSEMBLY-56?page=all ]
Gilles Scokart updated MASSEMBLY-56:
Attachment: MASSEMBLY-56.patch
> Refactor DirectoryMojo so it can be run either stand-alone or attached
> -
1 - 100 of 110 matches
Mail list logo
