Hi
Got the exact same issue with another plugin.
Le 18 juil. 2013 06:43, "Brett Porter" a écrit :
> Hi,
>
> I've got a regression here using the Swagger Maven Plugin [1] that looks
> different to the Aether one. Before I go poking around further, I was
> wondering if anyone can tell me if it's a
Hi,
I've got a regression here using the Swagger Maven Plugin [1] that looks
different to the Aether one. Before I go poking around further, I was wondering
if anyone can tell me if it's a regression on the Maven (and dependencies) end,
or something expected to be updated in the plugin?
[ERROR
Great link, but what links to it? I would certainly have viewed that page
if it was accessible and visible through the site's home page.
On Wed, Jul 17, 2013 at 3:01 PM, Hervé BOUTEMY wrote:
> Le mercredi 17 juillet 2013 14:13:38 Paul Benedict a écrit :
> > Is 3.0.5 still the preferred version?
Le mercredi 17 juillet 2013 14:13:38 Paul Benedict a écrit :
> Is 3.0.5 still the preferred version? I ask because the right-hand aside is
> still "Get Maven 3.0.5" -- which makes sense if 3.1 is not GA, but I think
> it is, right?
>
> PS: None of the release-notes.html pages include the release d
Just checking the ci-aggregator job [1]
I noticed is has been disabled with the following message:
"Disabled until you work out how not to use up all the storage on the
server."
I think we first need to resolve this before asking to install M3.1
In the meantime I'll try to execute it on my mac
-
Arnaud
Le 17 juil. 2013 à 21:14, Paul Benedict a écrit :
> Is 3.0.5 still the preferred version? I ask because the right-hand aside is
> still "Get Maven 3.0.5" -- which makes sense if 3.1 is not GA, but I think
> it is, right?
>
For me the GA status is mainly related to the status of
Is 3.0.5 still the preferred version? I ask because the right-hand aside is
still "Get Maven 3.0.5" -- which makes sense if 3.1 is not GA, but I think
it is, right?
PS: None of the release-notes.html pages include the release date. Can this
information be added (in the future)? It is difficult to
Hi,
The vote has passed with the following result:
+1 (binding): Hervé BOUTEMY, Olivier Lamy, Robert Scholte
+1 (non binding): Tony Chemit
-1 (non binding): Mirko Friedenhagen
I will promote the artifacts to the central repo.
Op Fri, 12 Jul 2013 23:12:02 +0200 schreef Robert Scholte
:
Hi
+1
Op Fri, 12 Jul 2013 23:12:02 +0200 schreef Robert Scholte
:
Hi,
We solved 3 issues:
http://jira.codehaus.org/secure/ReleaseNote.jspa?projectId=11530&styleName=Html&version=19426
There are still a couple of issues left in JIRA:
http://jira.codehaus.org/secure/IssueNavigator.jspa?reset=tr
Le mardi 16 juillet 2013 22:42:23 sebb a écrit :
> On 16 July 2013 22:37, Jason van Zyl wrote:
> > Typo on my part. There are 48 things to change when updating a release.
> >
> > I updated and triggered the publish an hour ago. I'm not sure when/how it
> > updates.
> Should be immediate (within a
I think I've boiled it down to a site plugin issue and reported
http://jira.codehaus.org/browse/MSITE-695
But no Maven 3.1 for Log4j 2 for now...
Gary
On Wed, Jul 17, 2013 at 12:17 PM, Anthony Dahanne wrote:
> hello
> did you check this page out :
> https://cwiki.apache.org/confluence/display
hello
did you check this page out :
https://cwiki.apache.org/confluence/display/MAVEN/AetherClassNotFound
Regarding maven site plugin, it says that 3.3 is compatible with 3.1
HTH,
Anthony
On Wed, Jul 17, 2013 at 12:13 PM, Gary Gregory wrote:
> If you check out log4j 2 trunk and run: mvn clean si
Hm, I do see here:
https://cwiki.apache.org/confluence/display/MAVEN/AetherClassNotFound
that the site plugin needs to be updated, but we cannot do that because it
causes a NullPointerException in site:stage-deploy.
Gary
On Wed, Jul 17, 2013 at 12:13 PM, Gary Gregory wrote:
> If you check out
If you check out log4j 2 trunk and run: mvn clean site, you get a
java.lang.NoClassDefFoundError. Shouldn't this work out of the box? All is
well with 3.0.5. Should I configure something magic or create a JIRA?
[INFO] Scanning for projects...
[INFO]
That would likely be a fix that any organizations providing longer term
support would likely backport for their enterprise versions of Jenkins...
On 17 July 2013 10:53, Arnaud Héritier wrote:
> Note that to have the fix and be able to use Maven 3.1.0, jenkins users
> will have to upgrade which
Note that to have the fix and be able to use Maven 3.1.0, jenkins users
will have to upgrade which won't be soon for many of them
(Myself I'm using the latest really stable one : the 1.480 LTS)
On Wed, Jul 17, 2013 at 11:31 AM, Stephen Connolly <
stephen.alan.conno...@gmail.com> wrote:
> On 17 J
On 17 July 2013 10:09, Olivier Lamy wrote:
> 2013/7/17 Olivier Lamy :
> > 2013/7/17 Stephen Connolly :
> >> On 16 July 2013 23:01, Arnaud Héritier wrote:
> >>
> >>> > >
> >>> >
> >>> > Until Jenkins gets upgraded to 1.520+ at which point the (crappy in
> my
> >>> > personal view) Maven job type
2013/7/17 Olivier Lamy :
> 2013/7/17 Stephen Connolly :
>> On 16 July 2013 23:01, Arnaud Héritier wrote:
>>
>>> > >
>>> >
>>> > Until Jenkins gets upgraded to 1.520+ at which point the (crappy in my
>>> > personal view) Maven job type will be unable to run 1.5
>>> >
>>> >
>>> The crappy one which
Hello there,
2013/7/16 Chris Graham
> On Tue, Jul 16, 2013 at 6:26 PM, Lennart Jörelid
> wrote:
>
> > This is not (or should not be) an entirely technical question - support
> for
> > various versions of JDK may be the simpler criterion to discuss, but I
> feel
> > the more relevant question is
19 matches
Mail list logo
