Olivier Lamy wrote:
Note the EOSL of the 1.4 this means you have to be regitered to get
this old and not any more supported java version.
The archive [0] can still be accessed without registration.
Benjamin
[0] http://java.sun.com/products/archive/
Personnally, I have always used a 1.4 jdk (and always use 1.4) to
cut/build a maven stuff release.
You can get one here http://java.sun.com/j2se/1.4.2/download.html
Note the EOSL of the 1.4 this means you have to be regitered to get
this old and not any more supported java version.
--
Olivier
20
You'd need to use animal sniffer to ensure that you're not using 1.5 or 1.6
only methods (e.g. String.isEmpty(), etc)
2009/3/20 Barrie Treloar
> I vaguely remember that 1.4 should be used but I can't find anything
> on Committer Environment or Committer Settings.
>
> Does that mean the compiler
I vaguely remember that 1.4 should be used but I can't find anything
on Committer Environment or Committer Settings.
Does that mean the compiler settings configured in the parent poms is
good enough?
My machine recently went boom so I have re-installed and I only have
JDK 1.6.0_11.
-
jerome lacoste wrote:
> Note I am not trying to be a pain in the butt here.
:) I meant I know the fact that the issue could have been moved up to
2.0.1 was the pain, not you.
> I am just saying
> that there was something that could have been done better and that I
> hope won't happen again.
I'
On 2/1/06, Brett Porter <[EMAIL PROTECTED]> wrote:
> jerome lacoste wrote:
> > Sorry but it's not marked as such in Jira
> >
> > http://jira.codehaus.org/browse/MASSEMBLY-19
> >
> > Component/s: None
> > Affects Version/s:None
> > Fix Version/s:None
> >
>
> I know its a pain i
jerome lacoste wrote:
> Sorry but it's not marked as such in Jira
>
> http://jira.codehaus.org/browse/MASSEMBLY-19
>
> Component/s: None
> Affects Version/s:None
> Fix Version/s:None
>
I know its a pain in the butt, but I will reiterate. We created the JIRA
projects *after
On 1/30/06, Brett Porter <[EMAIL PROTECTED]> wrote:
> As I explained in response to your previous message, we already do that.
> You fixes were scheduled for, and always have been scheduled for 2.1.
Sorry but it's not marked as such in Jira
http://jira.codehaus.org/browse/MASSEMBLY-19
Component/
As I explained in response to your previous message, we already do that.
You fixes were scheduled for, and always have been scheduled for 2.1.
2.1 has not been delayed in any way. 2.0.1 was pushed up with some bug
fixes that were represented as more critical.
As soon as the outstanding 2.1 bugs/f
"When a milestone is about to be released, there should probably be a
way for us bug reporters to know. That's why I proposed to use Jira:
targeting an issue to a future release will notify me and I can react."
+1
-
To unsubsc
Hi,
I've had a little issue with regard to the latest release of maven
assembly plugin. Mostly because some issues I had reported and fixed
almost 3 months ago didn't make it into the release.
So I am being told that 1- there was a description of the issues to be
fixed, and 2- there was a 72h vot
I think the other issue is related. The poms directory isn't group
writeable and the group is wrong
On Thu, 8 Jul 2004 14:08:33 +1000, Brett Porter <[EMAIL PROTECTED]> wrote:
> I can try it later... any more info you have above the FAILURE? -e output useful?
>
> - Brett
>
>
>
> Quoting Dion G
I can try it later... any more info you have above the FAILURE? -e output useful?
- Brett
Quoting Dion Gillard <[EMAIL PROTECTED]>:
> On Thu, 8 Jul 2004 13:16:38 +1000, Brett Porter <[EMAIL PROTECTED]> wrote:
> > Running which goal? What was the actual error?
>
> scm:perform-release, during th
On Thu, 8 Jul 2004 13:16:38 +1000, Brett Porter <[EMAIL PROTECTED]> wrote:
> Running which goal? What was the actual error?
scm:perform-release, during the plugin:repository-deploy step.
> It has always worked for me, with the exception of the occasional "cvs: protocol
> error data discarded", b
Running which goal? What was the actual error?
It has always worked for me, with the exception of the occasional "cvs: protocol
error data discarded", by which you just have to run it again (CVS server bug).
- Brett
Quoting Dion Gillard <[EMAIL PROTECTED]>:
> When I was doing the release for th
When I was doing the release for the NSIS plugin today, I got the following:
BUILD FAILED
File.. C:\Documents and Settings\Dion
Gillard\.maven\cache\maven-scm-plugin-1.4.1-SNAPSHOT\plugin.jelly
Element... maven:maven
Line.. 158
Column 9
Unable to obtain goal [plugin:repository-deploy]
> Yeah, except that I've found that if you don't do this, some
> people forget about it. This is same as for 11/. It doesn't
> harm to do it I think.
>
> The reason it was leading to releases with no changes was
> that the plugins were tied to the Maven release. This is no
> longer true.
>
Ex
> -Original Message-
> From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]
> Sent: 15 December 2003 06:20
> To: Maven Developers List
> Subject: RE: Releasing Plugins
>
> "Vincent Massol" <[EMAIL PROTECTED]> wrote on 14/12/2003 09:39:24
AM:
>
"Vincent Massol" <[EMAIL PROTECTED]> wrote on 14/12/2003 09:39:24 AM:
> Hi Jason,
>
> Cool. Here's my checklist (from the top of my head):
>
> 1/ modify project.xml and remove -SNAPSHOT
> 2/ modify project.xml to change the : move HEAD to
> MAVEN_[plugin name]_[version major]_[version minor]
> 3
;Maven Developers List'
> Subject: RE: Releasing Plugins
>
>
> Hi Jason,
>
> Cool. Here's my checklist (from the top of my head):
>
> 1/ modify project.xml and remove -SNAPSHOT
> 2/ modify project.xml to change the : move HEAD to
> MAVEN_[plugin name]_[version
m: Jason van Zyl [mailto:[EMAIL PROTECTED]
> Sent: 09 December 2003 02:22
> To: Maven Developers List
> Subject: Releasing Plugins
>
> Vincent,
>
> I was going to release the FAQ plugin for Martin and was wondering
what
> you've been doing. Figure I would try to quickly in
Vincent,
I was going to release the FAQ plugin for Martin and was wondering what
you've been doing. Figure I would try to quickly integrate your
procedure into the release plugin and use that. I think Brett's SCM
plugin can deal with the tagging and such so if you don't have something
automated I'
On Tue, 2003-06-10 at 12:40, Vincent Massol wrote:
> > -Original Message-
> > From: Jason van Zyl [mailto:[EMAIL PROTECTED]
> > Sent: 10 June 2003 16:41
> > To: Maven Developers List
> > Subject: Re: Process for releasing plugins
> >
> > On Tue,
> -Original Message-
> From: Jason van Zyl [mailto:[EMAIL PROTECTED]
> Sent: 10 June 2003 16:41
> To: Maven Developers List
> Subject: Re: Process for releasing plugins
>
> On Tue, 2003-06-10 at 10:32, Vincent Massol wrote:
> > Hi Maven developers,
> &g
On Tue, 2003-06-10 at 10:32, Vincent Massol wrote:
> Hi Maven developers,
>
> I have started a guide for releasing plugins:
> http://nagoya.apache.org/wiki/apachewiki.cgi?Maven/ReleasingPlugins
>
> What do you think about following it?
+1
Do you think you could actually mak
Hi Maven developers,
I have started a guide for releasing plugins:
http://nagoya.apache.org/wiki/apachewiki.cgi?Maven/ReleasingPlugins
What do you think about following it?
Comments on its content?
Note that the guide on the Maven development process pages
(http://maven.apache.org/development
26 matches
Mail list logo
