Sounds good to me!
/Anders
On Mon, May 4, 2015 at 8:52 PM, Baptiste Mathus wrote:
> OK, so, to try and sum up the discussions and reading the ML we currently
> have under http://mojo.codehaus.org/mail-lists.html, I think the current
> agreement is as follows:
>
>
>- Development List : alrea
+1
/Anders (mobile)
Den 4 maj 2015 15:37 skrev "Baptiste Mathus" :
> Hi,
>
> So, as a followup with the upcoming Codehaus shutdown, to go forward and
> try to attract attention to those who may have missed the other quite
> verbose threads .
>
> Let's
>
> Vote open for 72h max (don't know if we c
Anyone who knows if it actually possible for us to keep the groupId when
moving, as we don't own the codehaus.org domain? I think that most of us
can agree on it's best (at least in short term) and easier to keep the same
groupId. But can we really do that?
/Anders
On Mon, May 4, 2015 at 2:07 PM,
ects
> to migrate (which branches, which tags...) and I indeed thought that part
> could easily and more effectively be crowd sourced.
>
> 2015-05-04 10:33 GMT+02:00 Anders Hammar :
>
>> I also enriched the csv file describing the projects to migrate. Nicely
>>> presented
>
> I also enriched the csv file describing the projects to migrate. Nicely
> presented thanks to Github btw:
> https://github.com/mojohaus/convert-to-git/blob/master/repo-infos.csv
>
> Please add the mojos you want inside.
>
I've assumed we were going to include all mojos, at least all released
o
> There is no release in progress it seems, thus+1
> let's go.
>
There is a release of the jaxb2 mojo in progress.
/Anders
>
>
> On Sun, May 3, 2015 at 9:41 PM, Baptiste Mathus
> wrote:
>
>> Hi,
>>
>> As the deadline is coming close, and the migration script seems to work,
>> I'd like to *prop
+1
/Anders (mobile)
Den 3 maj 2015 21:49 skrev "Baptiste Mathus" :
> Hi all,
>
> As a followup to previous threads, I guess it's time for us to try and
> move on.
> Indeed, the announcement says services should be shut down the 17 May.
>
> So, to go forward, I'd like to ask Codehaus support to pu
to actually work with only the Maven
>> configuration instead of every plugin project developing special support
>> for Eclipse.
>>
>> That being said, if the Eclipse integration is decently simple, we could
>> certainly provide it. I would argue that such a solutio
Title: Message Title
Anders Hammar commented on an issue
Title: Message Title
Anders Hammar commented on an issue
Title: Message Title
Anders Hammar commented on an issue
Title: Message Title
Anders Hammar commented on an issue
Title: Message Title
Anders Hammar commented on an issue
integration works properly. Any Eclipse
> Developers out there are certainly encouraged to contribute, at least in
> letting me know how to test and verify that the j-m-p works with Eclipse. I
> added a screenshot of the Lifecycle mappings - as I can interpret them -
> from a vanilla
Title: Message Title
Anders Hammar commented on an issue
>
>
>
> schemagen
> testSchemagen
>
>
>
>
> true
> false
>
>
>
>
>
>
>
>
Title: Message Title
Anders Hammar commented on an issue
What happened to v2.0 of the jaxb-m-p? Also, I really think we need to
solve the m2e compat issue as that's a key thing for us on Eclipse (and it
worked in v1.x).
/Anders
On Wed, Apr 29, 2015 at 2:41 AM, Lennart Jörelid
wrote:
> Hello all,
>
> It seems we are in the transition between Codehaus
Title: Message Title
Anders Hammar commented on an issue
Title: Message Title
Anders Hammar reopened an issue
Title: Message Title
Anders Hammar commented on an issue
On Wed, Apr 22, 2015 at 11:02 PM, Lennart Jörelid wrote:
> Nopes. I don't use eclipse so can't really validate this.
>
> 2015-04-22 21:20 GMT+02:00 Anders Hammar :
>
>> Have you also looked into the m2e compatibility issue?
>>
>> /Anders (mobile)
>> Den
> Regards Mirko
>> --
>> http://illegalstateexception.blogspot.com/
>> https://github.com/mfriedenhagen/ (http://osrc.dfm.io/mfriedenhagen)
>> https://bitbucket.org/mfriedenhagen/
>>
>>
>> On Sun, Mar 1, 2015 at 5:17 PM, Anders Hammar wrote:
>> &
rs.list
> file with the mapping with your full name and email (not your github id,
> see others for example) so that when we redo the migration we can replace
> the svn user by the values on the right.
>
> HTH
> Cheers
>
>
> 2015-04-08 21:51 GMT+02:00 Anders Hammar :
>
sible with
> https://github.com/MojoHaus/convert-to-git/blob/master/mojo-committers.list
> to enrich and use it when we do the real migration.
> Le 8 avr. 2015 18:21, "Anders Hammar" a écrit :
>
>> Any problems if the svn user id doesn't match the github user id?
>>
lease add me (wguttmn) as well; I'd love to help with the move of
>>>>>>>>> the castor-maven-plugin (given that I have just moved the Castor code
>>>>>>>>> from
>>>>>>>>> Codehaus to github).
>>>>>>>>
And me please: andham
/Anders
On Fri, Mar 20, 2015 at 1:52 PM, Dennis Lundberg wrote:
> Please add me as well:
>
> dennisl
>
>
> On Fri, Mar 20, 2015 at 9:06 AM, Stefan Birkner
> wrote:
> > Please add me too: stefanbirkner
> >
> > 2015-03-20 9:02 GMT+01:00 Kristian Rosenvold :
> >> krosenvold
One of the reasons not moving to ASF is to keep the "process" much
simpler/lightweighter. At least that's how I've seen it so far. The
threshold to start a new plugin here at Mojos has been very small.
But I guess that could be changed. Maybe we could introduce something like
the sandbox over att
+1
/Anders
On Mon, Mar 2, 2015 at 8:51 AM, Baptiste Mathus
wrote:
> Well, since this didn't seem to trigger counter opinions I'm starting a
> formal vote.
>
> That vote is to deprecate the shitty-maven-plugin, and move it to the
> mojo's graveyard.
>
> [ ] +1 : deprecate it
> [ ] 0 : don't care
ding
an Eclipse distro. I have a very simple Maven project that I test it with
(its the xjc-main project from the ITs), which I could provide.
/Anders
On Tue, Feb 10, 2015 at 8:32 AM, Anders Hammar wrote:
> I'll have a look.
>
> Also, I'm confused by the new type of debug lo
Hmmm. Is it only me that sees a problem with the org.codehaus.mojo groupId?
Can we continue to use that in the future when syncing to central?
Other than that I guess this is a good time to migrate to git instead of
svn.
/Anders
On Fri, Feb 27, 2015 at 10:38 AM, David Karlsen
wrote:
> Codehaus
For some reason I can't mark version tidy-maven-plugin-1.0-beta-1 as
released. Could someone do that please?
/Anders
On Mon, Feb 23, 2015 at 11:00 PM, Anders Hammar (JIRA)
wrote:
> Anders Hammar
> <https://jira.codehaus.org/secure/ViewProfile.jspa?name=afloom> *up
Title: Message Title
Anders Hammar updated an issue
Title: Message Title
Anders Hammar created an issue
Title: Message Title
Anders Hammar created an issue
>
> I would recommend that we migrate to the following requirement for all our
> plugins:
>
>1. Minimum Maven version 3.0.4 (i.e. drop support for Maven 2.x)
>
> As discussed (and concluded) somewhere else, we should go with a Maven 3.0
minimum requirement. Unless there is a good technical reas
Title: Message Title
Anders Hammar updated an issue
Title: Message Title
Anders Hammar created an issue
Title: Message Title
Anders Hammar created an issue
Title: Message Title
Anders Hammar created an issue
Title: Message Title
Anders Hammar created an issue
are considerably better log statements for
> jaxb2-maven-plugin users when attempting to track down problems in their
> configuration than traditional Maven logging-style statements.
> Of course, these boxes stand out a tad from the traditional logging
> statements - which is intentiona
and what should be done?
> Like a log trace, and possibly some poinpoint-the-error-time?
>
>
> 2015-02-09 22:44 GMT+01:00 Anders Hammar :
>
>> -1
>>
>> The m2e integration doesn't work. I've only tested the xjc mojo so far
>> though. The problem can be s
Title: Message Title
Anders Hammar commented on an issue
-1
The m2e integration doesn't work. I've only tested the xjc mojo so far
though. The problem can be seen by importing IT 'xjc-main' for example.
/Anders
On Mon, Feb 9, 2015 at 7:35 AM, Lennart Jörelid
wrote:
> Hi all,
>
> I'd like to release version 2.0 of the JAXB2 Maven Plugin, which is a
>
Title: Message Title
Anders Hammar created an issue
Title: Message Title
Anders Hammar updated an issue
Title: Message Title
Anders Hammar updated an issue
Title: Message Title
Anders Hammar commented on an issue
Title: Message Title
Anders Hammar created an issue
Title: Message Title
Anders Hammar created an issue
Title: Message Title
Anders Hammar created an issue
Title: Message Title
Anders Hammar created an issue
Title: Message Title
Anders Hammar updated an issue
Title: Message Title
Anders Hammar created an issue
Title: Message Title
Anders Hammar created an issue
I'm fine with that.
A generic discussion around this for Mojo would be good, like we did over
att Apache Maven. And then update the dev guidelines.
/Anders
On Wed, Feb 4, 2015 at 9:59 AM, Sergei Ivanov wrote:
> Hi Lennart,
>
> Yes to all three from me: it is time to move on and ditch the legacy
Title: Message Title
Anders Hammar reopened an issue
Title: Message Title
Anders Hammar commented on an issue
Title: Message Title
Anders Hammar commented on an issue
rect when I'm trying to
> log in at the Kinai JIRA.
> I don't seem to be able to access the issue tracker there in logged in
> state.
>
> That's actually the reason I'm asking if you can acess/login/create an
> issue in the Kenai JIRA.
>
> :)
>
> 2015-0
Sure, I guess I could file a ticket. Just checking why you can't do it
yourself? I'm thinking that as you know the issue it would be than me being
a proxy. I don't have any extra privs in the Kenai JIRA that I know of.
/Anders
On Wed, Jan 14, 2015 at 7:58 PM, Lennart Jörelid
wrote:
> Hello all,
I'm fine with deprecating it. There has often been a "tradition" of having
external file for listing things, which IMHO is a Maven anti-pattern. All
configuration should be in the POM. (Most likely though it comes from some
use case where the file names are produced externally and put in a separate
Create an account here:
https://xircles.codehaus.org/signup/
/Anders
On Fri, Dec 5, 2014 at 2:30 PM, Dave Maughan
wrote:
> Hi,
>
> We have a requirement whereby we do not want the rpm build to fail if a
> source.location does not exist. We were doing the same previously by using
> the antrun pl
Title: Message Title
Anders Hammar commented on an issue
>>>>> Duh! I meant version 2.2.11, of course; just a typo on my part.
>>>>> However, in the 2.2.11 JAXB bom you will find the following:
>>>>>
>>>>> 1.7.7
>>>>>
>>>>> ... which is the root of my question. I c
Title: Message Title
Anders Hammar commented on an issue
Title: Message Title
Anders Hammar commented on an issue
Title: Message Title
Anders Hammar commented on an issue
>> javax.activation
>> activation
>>
>> stax-api
>> javax.xml.stream
>>
>>
>
Title: Message Title
Anders Hammar commented on an issue
>
>
>1. The org.glassfish.jaxb:jaxb-runtime:2.2.12 depends on the artifact
>org.jvnet.staxex:stax-ex:1.7.7 which I can't find in repo1. (Version 1.7.6
>is present, though). I can test refactoring the plugin using the 1.7.6
>version, but I would rather that the normal dependency set
Title: Message Title
Anders Hammar commented on an issue
Title: Message Title
Anders Hammar commented on an issue
Title: Message Title
Anders Hammar commented on an issue
Title: Message Title
Anders Hammar commented on an issue
mojo-parent looks good wrt list archives. Go ahead and roll...
/A
On Wed, Sep 24, 2014 at 8:40 AM, Anders Hammar wrote:
> Please hold on that for a while. I want to verify that the mailing lists
> are specified correctly and are in sync with what's specified on the site
> (or
Please hold on that for a while. I want to verify that the mailing lists
are specified correctly and are in sync with what's specified on the site
(or the other way around). There are some MOJO tickets for this.
/Anders
On Wed, Sep 24, 2014 at 7:57 AM, Hervé BOUTEMY
wrote:
> I'd like to release
Title: Message Title
Anders Hammar reopened an issue
Title: Message Title
Anders Hammar commented on an issue
Search.maven.org is handled by Sonatype and is a different story. Don't
write a HAUS ticket for that.
You could file a ticket at issues.Sonatype.org
/Anders (mobile)
Den 16 sep 2014 06:55 skrev "Lennart Jörelid" :
> Hello Karl,
>
> Is that really applicable in this case?
>
> The artifact *is* p
No need to respin IMO as the correct info is in the mail thread.
/Anders (mobile)
Den 10 sep 2014 14:24 skrev "Lennart Jörelid" :
> Bon Jour, Baptiste.
>
> I simply missed pasting the explicit (version-specfic) link to the staging
> repository of the a-m-p version 1.7 into the vote email,
> but I
Title: Message Title
Anders Hammar commented on an issue
Title: Message Title
Anders Hammar commented on an issue
I can't even log in to Bamboo. :-(
/Anders
On Mon, Sep 8, 2014 at 4:55 PM, Dan Tran wrote:
> Hi
>
> Please give me permission to add more plugin into baaboo ci,
>
> or if it is too much of a hassle, please add
>
> dbupgrade, vfs, and wagon-maven-plugin into CI
>
> Thanks
>
> -Dan
>
>
Ah, I forgot. Mark position was that there shouldn't be any need for using
tools.jar directly today (JDK 7 or 8 I guess) as everything should be
possible through the JDK API. Dare you challenge him? ;-)
/Anders
On Mon, Sep 8, 2014 at 10:25 AM, Anders Hammar wrote:
> Me and Dennis t
d from JDK 9, we will need to
> include whatever jar/module that contains the javadoc classes in the JDK 9
> distribution to make *ajdoc* work.
>
> As far as I can see, this implies some adaption in the way that the a-m-p
> works.
>
>
> 2014-09-08 9:03 GMT+02:00 Anders Hammar
>> aspectj_maven_plugin
>>>>>>> is compiled using different kinds of JDKs. This is to validate that
>>>>>>> the
>>>>>>> AspectJ compiler options for the respective JDKs do not cause
>>>>>>>
>>>>>>> java.lang.Unsuppor
The release notes are for v1.2.1!?
/Anders (mobile)
Den 7 sep 2014 12:45 skrev "Javier Murciego" :
> Hi,
>
>
> I'd like to release version 1.2.2 of the WAS6 maven plugin
>
>
> the plugin is quite stable and there are only one new issue in the last 8
> months,:
>
>
> https://jira.codehaus.org/secu
One problem is that the JIRA URL is on the produced mojo site, so creating
the JIRA project after the release requires a new release to update the
site.
/Anders
On Wed, Sep 3, 2014 at 9:31 AM, Dan Tran wrote:
> Correct
>
> -Dan
>
>
> On Tuesday, September 2, 2014, An
Not sure what you mean. Do you want to make a 1.0 release without a mojo
specific JIRA project?
/Anders
On Wed, Sep 3, 2014 at 8:29 AM, Dan Tran wrote:
> Currently in order for a component to become 1.0, it just have a Jira
> project. So far we have a hard time getting depot to manage this pro
I filed a ticket for this:
http://jira.codehaus.org/browse/MASPECTJ-135
Feel free to add more info as you see fit.
/Anders
On Wed, Aug 20, 2014 at 3:56 PM, Dan Tran wrote:
> Hi Sergei, you are right, i have a convenient script to 'cd' into my dev
> tree like this
>
> @echo off
> cd c:\views\d
Title: Message Title
Anders Hammar created an issue
Title: Message Title
Anders Hammar updated an issue
IT could very well be some OS related issue in the ITs. Just to guess, in
this case it could be something related to '/' vs '\' as paths looks to be
involved. Most devs are not Windows and would notice this.
/Anders
On Wed, Aug 20, 2014 at 8:04 AM, Dan Tran wrote:
> not sure why, but i am not
Title: Message Title
Anders Hammar commented on an issue
Title: Message Title
Anders Hammar closed an issue as Won'
Title: Message Title
Anders Hammar commented on an issue
> And also bump the language level to 1.5 if it is still 1.4
>
Java 5 is set by default by the latest mojo-parent, so go with that and
remove anything overriding it in the mojo's pom.
/Anders
>
>
> On 22 July 2014 08:08, Anders Hammar wrote:
>
>> And also bump
And also bump the maven req to 2.2.1+? I'm fine with that.
/Anders
On Tue, Jul 22, 2014 at 9:03 AM, Dan Tran wrote:
> Hi
>
> Any objection to use maven api 2.2.1 instead of 2.0.6 for a exec-m-p and
> build-helper.?
>
> No particular reason
>
> Thanks
>
> -D
>
1 - 100 of 1100 matches
Mail list logo
