[ http://jira.codehaus.org/browse/MNGECLIPSE-79?page=comments#action_60196
]
Eugene Kuleshov commented on MNGECLIPSE-79:
---
In embedder 2.0.3 after executing:
mavenEmbedder.execute(mavenProject, goals, eventMonitor, transferListener,
properties, f.
we'll make sure they don't do ;) the version in svn is becoming clear
On 3/5/06, Brett Porter <[EMAIL PROTECTED]> wrote:
> Sure, but they don't really need to redistribute half of eclipse themselves.
>
> - Brett
>
> Carlos Sanchez wrote:
> > servicemix is in progress of migrating to m2 and theri a
[ http://jira.codehaus.org/browse/MNG-2123?page=comments#action_60195 ]
Carlos Sanchez commented on MNG-2123:
-
if I add a dependency in 1.6 it breaks, so I can't force a version in my pom
Maven version: 2.0.3-SNAPSHOT
[DEBUG] Building Maven user-level
Excellent, I'll go that route.
Wayne
On 3/6/06, Brett Porter <[EMAIL PROTECTED]> wrote:
> Obviously a very late reply to this, but I'd like to suggest that you
> ask glassfish to publish these to the java.net repository. It's very
> easy for them to do, Kohsuke looks after it, and we are plannin
[ http://jira.codehaus.org/browse/MNG-2123?page=all ]
Carlos Sanchez updated MNG-2123:
Fix Version: 2.0.4
> NullPointerException when a dependency uses version range and another uses an
> actual version incompatible with that range
> ---
[ http://jira.codehaus.org/browse/MNG-2123?page=comments#action_60194 ]
Carlos Sanchez commented on MNG-2123:
-
if I add a dependency to commons-digester 1.7 it works
> NullPointerException when a dependency uses version range and another uses an
> actua
NullPointerException when a dependency uses version range and another uses an
actual version incompatible with that range
-
Key: MNG-2123
URL: http://jira.code
Sure, but they don't really need to redistribute half of eclipse themselves.
- Brett
Carlos Sanchez wrote:
> servicemix is in progress of migrating to m2 and theri artifacts will
> be at org.apache.servicemix groupid
>
> On 3/5/06, Brett Porter <[EMAIL PROTECTED]> wrote:
>> Moderation is somethi
Obviously a very late reply to this, but I'd like to suggest that you
ask glassfish to publish these to the java.net repository. It's very
easy for them to do, Kohsuke looks after it, and we are planning to sync
it in automatically.
https://maven-repository.dev.java.net/
- Brett
Wayne Fay wrote:
servicemix is in progress of migrating to m2 and theri artifacts will
be at org.apache.servicemix groupid
On 3/5/06, Brett Porter <[EMAIL PROTECTED]> wrote:
> Moderation is something we'd all like. Getting there.
>
> This is not pretty. I will find out what's going on.
>
> - Brett
>
> Giorgio Gall
[ http://jira.codehaus.org/browse/MJAVADOC-51?page=comments#action_60193 ]
Maria Odea Ching commented on MJAVADOC-51:
--
Already fixed in svn, the maven website just needs to be updated.
> Wrong source url on website
> ---
>
>
Moderation is something we'd all like. Getting there.
This is not pretty. I will find out what's going on.
- Brett
Giorgio Gallo wrote:
> Hi!
>
> I'm sorry to write at an inappropriate address (got this from
> http://maven.apache.org/project-faq.html) - I just couldn't find
> anything like [EMA
I've noted it to take a particularly look (if not by me, someone else).
I guess february snuck by and I didn't do the plugin health update. I'll
do that tomorrow. I'll put jar on the feb rotation if it isn't already.
We have a very large number of patches that haven't been dealt with.
Just wanted
Since we've voted to do this, I'm just going to give people 48 hours to
object to these particular names.
[see MPA-50]
Our dev list traffic has gone nuts. Let's create:
[EMAIL PROTECTED]
* this will be for CI, error reports from the repository manager, and so on
* depending on policy, this may
create new Maven dev lists
--
Key: MPA-50
URL: http://jira.codehaus.org/browse/MPA-50
Project: Maven Project Administration
Type: Task
Reporter: Brett Porter
Assigned to: Brett Porter
Fix For: 2006-q1
our dev list traffic has gon
+1
That means everyone is pretty much in favour.
I'll send a separate email with the proposed lists.
- Brett
Jason van Zyl wrote:
> Hi,
>
> I just wanted to close this up as I think it's a good idea and anything
> that let's people manage their mail better IMO is a good thing.
>
> +1
>
> In
[ http://jira.codehaus.org/browse/MNGECLIPSE-29?page=comments#action_60190
]
Eugene Kuleshov commented on MNGECLIPSE-29:
---
Folks, please contact me ASAP if you'd like to test dev build from behind proxy
or for using private repositories declared in
Can you please submit these to jira? There are already some there
(MJAR), so please check for existing ones first.
Geoffrey De Smet wrote:
> For networktools.sf.net I used the webstart plugin,
> which uses the jar plugin to sign jars.
> I 've had a bunch of problems, most of wrong configuration on
[ http://jira.codehaus.org/browse/MPIR-29?page=all ]
Brett Porter updated MPIR-29:
-
Fix Version: 2.0
> Invalid groupId in dependency pom fails dependencies report with an IAE
> ---
>
>
[ http://jira.codehaus.org/browse/MPIR-12?page=all ]
Brett Porter updated MPIR-12:
-
Fix Version: 2.0
> Dutch (NL) translation for site and reports plugins
> ---
>
> Key: MPIR-12
> URL: http://
[ http://jira.codehaus.org/browse/MPIR-19?page=all ]
Brett Porter updated MPIR-19:
-
Fix Version: 2.0
> Site plugin doesn't handle pom.xml in maven 1 version.
> --
>
> Key: MPIR-19
> URL: h
[ http://jira.codehaus.org/browse/MPIR-21?page=all ]
Brett Porter updated MPIR-21:
-
Fix Version: 2.0
> no generated for archive URL
> --
>
> Key: MPIR-21
> URL: http://jira.codehaus.org/browse/MPIR-21
>
[ http://jira.codehaus.org/browse/MPIR-11?page=all ]
Brett Porter updated MPIR-11:
-
Fix Version: 2.0
> improved dependency report
> --
>
> Key: MPIR-11
> URL: http://jira.codehaus.org/browse/MPIR-11
> Project: M
[ http://jira.codehaus.org/browse/MPIR-17?page=comments#action_60189 ]
Brett Porter commented on MPIR-17:
--
I think this is a worthwhile addition, but not on by default.
> Create XML documents containing report data.
> ---
Is this MJAR-32?
Pablo wrote:
> Hello everyone
>
> I tried to use JarSignMojo from maven-jar-plugin trunk but with no success.
> Out of the box it's not useable.
> 1) If I set verify to true the following code is done:
>if ( verify )
>{
>JarSignVerifyMojo verify = new
[ http://jira.codehaus.org/browse/MNG-2098?page=comments#action_60188 ]
Brett Porter commented on MNG-2098:
---
from dev@:
Setting the repository is not exactly a side effect of resolving metadata, but
I see why its a bug.
However, the collector can't selec
It's not exactly a side effect, but I see why its a bug. The collector
can't select the repository as it doesn't know where it will be present.
The current logic is based on the use of snapshots - it considered that
releases would only be in one so the first found is used, whereas for
snapshots al
[ http://jira.codehaus.org/browse/MNGECLIPSE-20?page=comments#action_60187
]
Eugene Kuleshov commented on MNGECLIPSE-20:
---
Same problem with embedder 2.0.3
> using ${version} for subproject dependencies doesn't work (maven uses 2.4.1
> version ins
[ http://jira.codehaus.org/browse/MNGECLIPSE-19?page=comments#action_60186
]
Eugene Kuleshov commented on MNGECLIPSE-19:
---
Mark, can you please elaborate what are you truing to do with such project
organization?
It doesn't seem your example is rele
[ http://jira.codehaus.org/browse/MNGECLIPSE-10?page=all ]
Eugene Kuleshov closed MNGECLIPSE-10:
-
Resolution: Fixed
Fix Version: (was: 1.0.0)
0.0.6
This had been fixed in embedder 2.0.3. Attached example is working now.
Hi,
Caught this later, even though its older than the other message I just
replied to. Thunderbird thought it was an email scam :)
So, are you suggesting that Maven users that want to try this need only
run dijjer locally, and then change their repository URL to
http://127.0.0.1:9115/http://repo1
Sorry for the late reply.
The default is to be a singleton, but I think it only lives as long as
it's ref count is > 0. So you probably want to set it to the true
singleton. I remember seeing someone note this recently for something
else, but I don't know if it exists in the current version of Mav
[ http://jira.codehaus.org/browse/MSUREFIRE-73?page=all ]
Brett Porter closed MSUREFIRE-73:
-
Assign To: Brett Porter
Resolution: Fixed
Fix Version: (was: 2.1.3)
2.2
somehow I already fixed this. Confirmed broken on tr
[ http://jira.codehaus.org/browse/MWAR-12?page=comments#action_60182 ]
Brett Porter commented on MWAR-12:
--
Scott, IIUC your solution will only work for WARs, and will break resources for
JARs.
We agreed on dev@maven.apache.org that classpath resources and
systemClassLoader.getResource returns null
--
Key: MSUREFIRE-73
URL: http://jira.codehaus.org/browse/MSUREFIRE-73
Project: Maven 2.x Surefire Plugin
Type: Bug
Versions: 2.1.3
Reporter: Carlos Sanchez
Priority:
[ http://jira.codehaus.org/browse/MSUREFIRE-73?page=comments#action_60181 ]
Carlos Sanchez commented on MSUREFIRE-73:
-
Attached test case
mvn test fails
ant test suceeds
> systemClassLoader.getResource returns null
>
Brian,
sorry for not replying sooner. Waay behind on mail.
Given the feedback on this thread, you can expect the vote will probably
be favourable. I'm gathering things up now to propose the necessary votes.
- Brett
Brian E. Fox wrote:
> I'd like to bump this back into current discussion. I'
Apologies for the late reply.
I think the key here is the perception of the dependency version. You
should actually declare what you need, not what you want :)
Basically, you shouldn't be upgrading to 1.0.1-SNAPSHOT on the core
release until such point as you actually want to use it from core. An
I'm personally sceptical that any kind of P2P based repository would
work effectively for Maven users.
That said, we'd certainly consider a contribution of a provider to use
it. Given there weren't any responses so far, I suspect that this isn't
a priority for others, but that might change.
I thi
Distribution:
http://maven.zones.apache.org/~maven/builds/trunk/m2-20060306.040001.tar.gz
Log:
http://maven.zones.apache.org/~maven/logs/trunk/m2-build-log-20060306.040001.txt
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For addit
Invalid jar manifest created
Key: MJAR-34
URL: http://jira.codehaus.org/browse/MJAR-34
Project: Maven 2.x Jar Plugin
Type: Bug
Environment: distributed maven 2.0.2
Reporter: Miguel Griffa
Priority: Blocker
I've found a bug I c
Distribution:
http://maven.zones.apache.org/~maven/builds/branches/maven-2.0.x/m2-20060306.031501.tar.gz
Log:
http://maven.zones.apache.org/~maven/logs/branches/maven-2.0.x/m2-build-log-20060306.031501.txt
-
To unsubscribe, e-mai
[ http://jira.codehaus.org/browse/MIDEA-14?page=all ]
Edwin Punzalan closed MIDEA-14:
---
Resolution: Fixed
> add support for ejb module configuration in iml
> ---
>
> Key: MIDEA-14
> URL: htt
Distribution:
http://maven.zones.apache.org/~maven/builds/trunk/m2-20060306.03.tar.gz
Log:
http://maven.zones.apache.org/~maven/logs/trunk/m2-build-log-20060306.03.txt
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For addit
[ http://jira.codehaus.org/browse/MSUREFIRE-69?page=comments#action_60176 ]
Jesse Kuhnert commented on MSUREFIRE-69:
Awesome, thanks Brett! I don't use a sun jvm so don't have the javadoc libs
available via normal means. (ibm's jre runs much much fas
[ http://jira.codehaus.org/browse/MASSEMBLY-56?page=comments#action_60175 ]
Allan Ramirez commented on MASSEMBLY-56:
Does somebody already came up with a good name for this? ;)
> Refactor DirectoryMojo so it can be run either stand-alone or attached
[ http://jira.codehaus.org/browse/MNG-2122?page=all ]
Brett Porter closed MNG-2122:
-
Assign To: Brett Porter
Resolution: Duplicate
MJAVADOC was the right place for this bug.
> Update web access and svn checkout URLS in source repository page of
>
Update web access and svn checkout URLS in source repository page of
maven-javadoc-plugin
-
Key: MNG-2122
URL: http://jira.codehaus.org/browse/MNG-2122
Project: Maven 2
Type: Tas
[ http://jira.codehaus.org/browse/MASSEMBLY-11?page=all ]
Allan Ramirez closed MASSEMBLY-11:
--
Resolution: Fixed
Fixed in SVN, usage of expressions are now allowed in the assembly descriptor.
> In a multi-module build, assembly descriptor paths ar
Distribution:
http://maven.zones.apache.org/~maven/builds/branches/maven-2.0.x/m2-20060306.024500.tar.gz
Log:
http://maven.zones.apache.org/~maven/logs/branches/maven-2.0.x/m2-build-log-20060306.024500.txt
-
To unsubscribe, e-mai
[ http://jira.codehaus.org/browse/MJAVADOC-55?page=all ]
Edwin Punzalan closed MJAVADOC-55:
--
Resolution: Fixed
Patch applied. Thanks.
> offline links not generated when offline
>
>
> Key: MJAVADOC-
[ http://jira.codehaus.org/browse/MASSEMBLY-11?page=all ]
Allan Ramirez updated MASSEMBLY-11:
---
Remaining Estimate: 4 hours
Original Estimate: 4 hours
> In a multi-module build, assembly descriptor paths are not project-relative,
> but erraneously
[ http://jira.codehaus.org/browse/MSUREFIRE-69?page=all ]
Brett Porter updated MSUREFIRE-69:
--
Attachment: pom.xml
> stop output to test-output directory
>
>
> Key: MSUREFIRE-69
> URL: http://jira.co
[ http://jira.codehaus.org/browse/MJAVADOC-55?page=all ]
Maria Odea Ching updated MJAVADOC-55:
-
Attachment: MJAVADOC-55-maven-javadoc-plugin.patch
> offline links not generated when offline
>
>
> Key:
[ http://jira.codehaus.org/browse/MIDEA-14?page=all ]
Edwin Punzalan updated MIDEA-14:
Assign To: Edwin Punzalan
Remaining Estimate: 4 hours
Original Estimate: 4 hours
> add support for ejb module configuration in iml
>
[ http://jira.codehaus.org/browse/MNGECLIPSE-85?page=comments#action_60168
]
Eugene Kuleshov commented on MNGECLIPSE-85:
---
Thorsten, can you please create patch that includes all new files. All you need
to do is to add these files to version contro
[ http://jira.codehaus.org/browse/MNGECLIPSE-85?page=all ]
Eugene Kuleshov updated MNGECLIPSE-85:
--
Comment: was deleted
> MavenLauncher should be externalized
>
>
> Key: MNGECLIPSE-85
> URL: htt
[ http://jira.codehaus.org/browse/MNGECLIPSE-85?page=all ]
Eugene Kuleshov updated MNGECLIPSE-85:
--
Comment: was deleted
> MavenLauncher should be externalized
>
>
> Key: MNGECLIPSE-85
> URL: htt
[ http://jira.codehaus.org/browse/MNGECLIPSE-85?page=all ]
Eugene Kuleshov updated MNGECLIPSE-85:
--
Comment: was deleted
> MavenLauncher should be externalized
>
>
> Key: MNGECLIPSE-85
> URL: htt
[ http://jira.codehaus.org/browse/MNGECLIPSE-85?page=all ]
Eugene Kuleshov updated MNGECLIPSE-85:
--
Comment: was deleted
> MavenLauncher should be externalized
>
>
> Key: MNGECLIPSE-85
> URL: htt
[ http://jira.codehaus.org/browse/MSUREFIRE-72?page=all ]
Brett Porter updated MSUREFIRE-72:
--
Fix Version: (was: 2.1.1)
2.2
> [surefire-testng] SurefireReportMojo.executeReport() throws a
> java.lang.NumberFormatException
> ---
[ http://jira.codehaus.org/browse/MSUREFIRE-69?page=comments#action_60167 ]
Jesse Kuhnert commented on MSUREFIRE-69:
I think it will ~probably~ be possible to build it with m2? There have to be
other projects with seperate source trees for differing
Distribution:
http://maven.zones.apache.org/~maven/builds/branches/maven-2.0.x/m2-20060306.003002.tar.gz
Log:
http://maven.zones.apache.org/~maven/logs/branches/maven-2.0.x/m2-build-log-20060306.003002.txt
-
To unsubscribe, e-mai
[ http://jira.codehaus.org/browse/MSUREFIRE-69?page=comments#action_60166 ]
Brett Porter commented on MSUREFIRE-69:
---
don't worry about uploads. I'll create snapshots from the cvs repository.
I haven't tried building testNG with m2, but I don't think it
Distribution:
http://maven.zones.apache.org/~maven/builds/trunk/m2-20060306.00.tar.gz
Log:
http://maven.zones.apache.org/~maven/logs/trunk/m2-build-log-20060306.00.txt
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For addit
[ http://jira.codehaus.org/browse/MSUREFIRE-69?page=all ]
Jesse Kuhnert updated MSUREFIRE-69:
---
Attachment: surefire-patch.txt
> stop output to test-output directory
>
>
> Key: MSUREFIRE-69
> URL: h
[ http://jira.codehaus.org/browse/MSUREFIRE-69?page=comments#action_60152 ]
Jesse Kuhnert commented on MSUREFIRE-69:
Got it now. Didn't realize TestNG was instantiated in two different places.
The patch supplied only works against the latest testng,
[surefire-testng] SurefireReportMojo.executeReport() throws a
java.lang.NumberFormatException
-
Key: MSUREFIRE-72
URL: http://jira.codehaus.org/browse/MSUREFIRE-72
Project: Maven 2.x
- Original Message -
From: "Wendy Smoak" <[EMAIL PROTECTED]>
To: "Maven Developers List"
Sent: Tuesday, February 28, 2006 4:00 PM
Subject: Re: [discussion] Improving poms on ibiblio
On 2/28/06, Grzegorz Słowikowski <[EMAIL PROTECTED]> wrote:
I analyzed ALL Tomcat 5.5.9, 5.5.12 and
Can't use two times a multiprojects in 2 differents goals
-
Key: MAVEN-1750
URL: http://jira.codehaus.org/browse/MAVEN-1750
Project: Maven
Type: Bug
Versions: 1.1-beta-3
Environment: 1.1-beta-3 from tr
Distribution:
http://maven.zones.apache.org/~maven/builds/trunk/m2-20060305.220001.tar.gz
Log:
http://maven.zones.apache.org/~maven/logs/trunk/m2-build-log-20060305.220001.txt
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For addit
Distribution:
http://maven.zones.apache.org/~maven/builds/branches/maven-2.0.x/m2-20060305.214501.tar.gz
Log:
http://maven.zones.apache.org/~maven/logs/branches/maven-2.0.x/m2-build-log-20060305.214501.txt
-
To unsubscribe, e-mai
[ http://jira.codehaus.org/browse/MNGECLIPSE-85?page=all ]
Thorsten Kamann updated MNGECLIPSE-85:
--
Attachment: ExecutePomAction.java.patch
> MavenLauncher should be externalized
>
>
> Key: MNGECLIPSE-85
[ http://jira.codehaus.org/browse/MNGECLIPSE-85?page=all ]
Thorsten Kamann updated MNGECLIPSE-85:
--
Attachment: DefaultMavenLauncher.java
> MavenLauncher should be externalized
>
>
> Key: MNGECLIPSE-85
>
[ http://jira.codehaus.org/browse/MNGECLIPSE-85?page=all ]
Thorsten Kamann updated MNGECLIPSE-85:
--
Attachment: IMavenLauncher.java
> MavenLauncher should be externalized
>
>
> Key: MNGECLIPSE-85
>
[ http://jira.codehaus.org/browse/MNGECLIPSE-85?page=all ]
Thorsten Kamann updated MNGECLIPSE-85:
--
Attachment: AbstractMavenLauncher.java
> MavenLauncher should be externalized
>
>
> Key: MNGECLIPSE-85
>
MavenLauncher should be externalized
Key: MNGECLIPSE-85
URL: http://jira.codehaus.org/browse/MNGECLIPSE-85
Project: Maven 2.x Extension for Eclipse
Type: Improvement
Components: Maven Launcher
Versions: 0.0.5
Repo
For networktools.sf.net I used the webstart plugin,
which uses the jar plugin to sign jars.
I 've had a bunch of problems, most of wrong configuration on my part,
but some I believe lay in the jar plugin.
In the end I changed these few lines in the jar plugin to get it
working, even if it's a qu
[ http://jira.codehaus.org/browse/MNG-32?page=all ]
Brett Porter updated MNG-32:
Priority: Blocker
Assign To: Jesse McConnell
Component: Sandbox
Plugin API
Design, Patterns & Best Practices
> Plugin test harness
> -
[ http://jira.codehaus.org/browse/MSUREFIRE-69?page=comments#action_60121 ]
Brett Porter commented on MSUREFIRE-69:
---
it should only require:
cd surefire-testng
vi pom.xml
mvn install
mvn -X might help.
I don't know how you go about getting testng int
I agree. I originally pushed this into 2.0.3 only to have it bumped, but
it needed more consideration.
We still need to look at Fabrizio's potential regression, and then cut
RC3 and start the vote over.
- Brett
Carlos Sanchez wrote:
> I'm +1 to release without MNG-1797. I'm not keen to so many l
Add a new goal for open the Jalopy's SettingsDialog
---
Key: MPJALOPY-11
URL: http://jira.codehaus.org/browse/MPJALOPY-11
Project: maven-jalopy-plugin
Type: New Feature
Reporter: Joachim Bader
Priority: Minor
[ http://jira.codehaus.org/browse/MSITE-74?page=comments#action_60119 ]
Gilles Scokart commented on MSITE-74:
-
Sorry, I don't have access to a proxy anymore. I can't test it for the moment.
> Suport proxy
>
>
> Key: MSITE-74
>
[ http://jira.codehaus.org/browse/MSUREFIRE-69?page=comments#action_60116 ]
Jesse Kuhnert commented on MSUREFIRE-69:
No I think you're right, I just think it's something I'm not completely in
control of. TestNG tries very hard to provide defaults tha
[ http://jira.codehaus.org/browse/MSUREFIRE-69?page=comments#action_60115 ]
Brett Porter commented on MSUREFIRE-69:
---
I was just saying that
new TestNG ( false )
is not a particularly help piece of code to read when used.
new TestNG()
testNG.setUseDef
Still playing with this rc with multiproject builds with a flat
layout: after the DefaultModelInheritanceAssembler fix everything work
as expected but I got my website broken due to a different behaviour
during publishing.
In my root module the website root directory is /x/htdocs. With the
previou
Distribution:
http://maven.zones.apache.org/~maven/builds/branches/maven-2.0.x/m2-20060305.171500.tar.gz
Log:
http://maven.zones.apache.org/~maven/logs/branches/maven-2.0.x/m2-build-log-20060305.171500.txt
-
To unsubscribe, e-mai
Hi,
Here's the result for m1 plugins releases: ejb & ear (I confirm the
EJB will be released as 1.7.2)
Mail thread:
http://www.nabble.com/-vote-m1-plugin-releases-t1208396.html#a3192380
Results: 4 Bindings: Arnaud, Emmanuel, Lukas, Stéphane
The releases will be done shortly.
Thanks,
Stéphane
Distribution:
http://maven.zones.apache.org/~maven/builds/trunk/m2-20060305.170001.tar.gz
Log:
http://maven.zones.apache.org/~maven/logs/trunk/m2-build-log-20060305.170001.txt
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For addit
John, please send a link to your latest build with MNG-1797 fixed when
available so I can test it and vote.
-Original Message-
From: John Casey [mailto:[EMAIL PROTECTED]
Sent: Friday, March 03, 2006 4:16 PM
To: Maven Developers List
Subject: Re: [vote] Release Maven 2.0.3 (second attempt)
This was a big one for me when adding the Perforce provider. The
"contract" for each method was undocumented and I had to look in other
providers to see what they were doing and mock that behavior, assuming
that behavior is correct...
-Original Message-
From: Brett Porter [mailto:[EMAIL P
[ http://jira.codehaus.org/browse/MSUREFIRE-69?page=comments#action_60113 ]
Jesse Kuhnert commented on MSUREFIRE-69:
Hi Brett,
The use of that method is decieving in it's current form. The default no args
constructor creates a default listener for h
Brett Porter wrote:
I've finally reviewed the dev process and made some edits. I made them
independently so they can relatively easily be rolled back.
a) Put the burden of merging on developers instead of a "release
manager". Changes need to go to the branch sooner and I think this is
what we we
Arnaud HERITIER wrote:
> Hi guys,
>
> Did you noticed that there was a problem with the 404 error page on the
> maven site if there is more than one level of directories in the erroneous
> address?
Yes. For m2, its in jira under MSITE
> Any idea to fix it ?
Absolute urls in those files.
-
On 3/5/06, Edwin Punzalan (JIRA) <[EMAIL PROTECTED]> wrote:
> [ http://jira.codehaus.org/browse/MIDEA-29?page=all ]
>
> Edwin Punzalan closed MIDEA-29:
> ---
>
> Assign To: Edwin Punzalan
> Resolution: Duplicate
>
> Ok, I'll close this duplicate issue now.
Hi guys,
Did you noticed that there was a problem with the 404 error page on the
maven site if there is more than one level of directories in the erroneous
address?
For example the error page is correct :
http://maven.apache.org/foo-index.html
http://maven.apache.org/foo/index.html
the
[ http://jira.codehaus.org/browse/MNG-32?page=comments#action_60105 ]
Jerome Lacoste commented on MNG-32:
---
Strangely, this issue doesn't have a priority (priority.none).
> Plugin test harness
> ---
>
> Key: MNG-32
> URL: h
[ http://jira.codehaus.org/browse/MIDEA-29?page=all ]
Edwin Punzalan closed MIDEA-29:
---
Assign To: Edwin Punzalan
Resolution: Duplicate
Ok, I'll close this duplicate issue now. Thanks.
> Wrong JDK selected (Maven 2.0.2/IDEA 5.1)
> ---
98 matches
Mail list logo
