12:21 p.m.
Hi,
Andrea reported that the 0.1.2 release (see [1]) contains the wrong version
number (0.2.0).
This artifact was already pushed to maven central.
On IRC we had the following idea:
* update master to 0.1.2-SNAPSHOT
* perform the release again (that hopefully will result in 0.1.2 on maven
central)
That still means we have a 0.2.0 on maven central. I will ask my contacts
at Sonatype to remove the 0.2.0 bits;
If folks are OK w/ that, I am happy to perform these steps by Monday morning
Greetings,
Matthias
[1] https://github.com/aerogear/aerogear-misc/blob/0.1.2/pom.xml
--
Matthias Wessendorf
blog: http://matthiaswessendorf.wordpress.com/
sessions: http://www.slideshare.net/mwessendorf
twitter: http://twitter.com/mwessendorf
12:30 p.m.
That is fine from my point of view.
This means that:
1) aerogear-parent 0.2.0 is broken until aerogear-misc 0.1.2 is released on
Central (it uses 0.1.2)
2) after aerogear-misc 0.2.0 is eventually removed from Central, we could
remove also the corresponding tag 0.2.0 from upstream repo
Thanks
Andrea
Matthias Wessendorf-2 wrote
Hi,
Andrea reported that the 0.1.2 release (see [1]) contains the wrong
version
number (0.2.0).
This artifact was already pushed to maven central.
On IRC we had the following idea:
* update master to 0.1.2-SNAPSHOT
* perform the release again (that hopefully will result in 0.1.2 on maven
central)
That still means we have a 0.2.0 on maven central. I will ask my contacts
at Sonatype to remove the 0.2.0 bits;
If folks are OK w/ that, I am happy to perform these steps by Monday
morning
Greetings,
Matthias
[1] https://github.com/aerogear/aerogear-misc/blob/0.1.2/pom.xml
--
Matthias Wessendorf
blog: http://matthiaswessendorf.wordpress.com/
sessions: http://www.slideshare.net/mwessendorf
twitter: http://twitter.com/mwessendorf
_______________________________________________
aerogear-dev mailing list
aerogear-dev@.jboss
--
View this message in context:
http://aerogear-dev.1069024.n5.nabble.com/aerogear-dev-aerogear-misc-rele...
Sent from the aerogear-dev mailing list archive at Nabble.com.
1:05 p.m.
I think that sounds reasonable.
On 9 May 2014 12:30, Andrea Vibelli <avibelli(a)redhat.com> wrote:
That is fine from my point of view.
This means that:
1) aerogear-parent 0.2.0 is broken until aerogear-misc 0.1.2 is released on
Central (it uses 0.1.2)
2) after aerogear-misc 0.2.0 is eventually removed from Central, we could
remove also the corresponding tag 0.2.0 from upstream repo
Thanks
Andrea
Matthias Wessendorf-2 wrote
> Hi,
>
> Andrea reported that the 0.1.2 release (see [1]) contains the wrong
> version
> number (0.2.0).
> This artifact was already pushed to maven central.
>
> On IRC we had the following idea:
> * update master to 0.1.2-SNAPSHOT
> * perform the release again (that hopefully will result in 0.1.2 on maven
> central)
>
> That still means we have a 0.2.0 on maven central. I will ask my contacts
> at Sonatype to remove the 0.2.0 bits;
>
> If folks are OK w/ that, I am happy to perform these steps by Monday
> morning
>
> Greetings,
> Matthias
>
> [1] https://github.com/aerogear/aerogear-misc/blob/0.1.2/pom.xml
>
> --
> Matthias Wessendorf
>
> blog: http://matthiaswessendorf.wordpress.com/
> sessions: http://www.slideshare.net/mwessendorf
> twitter: http://twitter.com/mwessendorf
>
> _______________________________________________
> aerogear-dev mailing list
> aerogear-dev@.jboss
> https://lists.jboss.org/mailman/listinfo/aerogear-dev
--
View this message in context:
http://aerogear-dev.1069024.n5.nabble.com/aerogear-dev-aerogear-misc-rele...
Sent from the aerogear-dev mailing list archive at Nabble.com.
_______________________________________________
aerogear-dev mailing list
aerogear-dev(a)lists.jboss.org
https://lists.jboss.org/mailman/listinfo/aerogear-dev
2:12 p.m.
What about:
1/ Release ag-misc 0.1.2 to Central to fix ag-parent
2/ Release ag-parent 0.2.1 to Central, using 0.2.0 of ag-misc
=> aligns minor version with ag-misc
=> Optionally: Adds checkstyle to pluginMngmt (AEROGEAR-358) (I can send a PR)
No deletes needed. Maven world will not collapse ;-)
Karel
On Fri, 9 May 2014 12:21:15 +0200
Matthias Wessendorf <mwessendorf(a)gmail.com> wrote:
Hi,
Andrea reported that the 0.1.2 release (see [1]) contains the wrong version
number (0.2.0).
This artifact was already pushed to maven central.
On IRC we had the following idea:
* update master to 0.1.2-SNAPSHOT
* perform the release again (that hopefully will result in 0.1.2 on maven
central)
That still means we have a 0.2.0 on maven central. I will ask my contacts
at Sonatype to remove the 0.2.0 bits;
If folks are OK w/ that, I am happy to perform these steps by Monday morning
Greetings,
Matthias
[1] https://github.com/aerogear/aerogear-misc/blob/0.1.2/pom.xml
5:45 p.m.
Great that we agree on 1), which is the most important.
@Karel: what change would you require about checkstyle plugin (just
wondering)?
It's already defined in the pluginManagement of jboss-parent, and it's
declared in the plugin of aerogear-parent, so it's inherited by all
projects.
The configuration of the plugin would be this one for every project:
<pluginManagement>
<plugins>
....
<plugin>
<artifactId>maven-checkstyle-plugin</artifactId>
<version>2.10</version>
</plugin>
...
</plugins>
</pluginManagement>
<plugin>
<artifactId>maven-checkstyle-plugin</artifactId>
<version>2.10</version>
<executions>
<execution>
<id>checkstyle-report</id>
<phase>process-classes</phase>
<goals>
<goal>check</goal>
</goals>
<configuration>
<includeTestSourceDirectory>true</includeTestSourceDirectory>
<configLocation>/checkstyle-rules.xml</configLocation>
<logViolationsToConsole>true</logViolationsToConsole>
<violationSeverity>error</violationSeverity>
</configuration>
</execution>
</executions>
<dependencies>
<dependency>
<groupId>org.jboss.aerogear</groupId>
<artifactId>aerogear-misc</artifactId>
<version>0.1.2</version>
<scope>compile</scope>
</dependency>
</dependencies>
<configuration>
<includeTestSourceDirectory>true</includeTestSourceDirectory>
<configLocation>/checkstyle-rules.xml</configLocation>
<logViolationsToConsole>true</logViolationsToConsole>
<violationSeverity>error</violationSeverity>
</configuration>
</plugin>
Thanks
Andrea
Karel Piwko wrote
What about:
1/ Release ag-misc 0.1.2 to Central to fix ag-parent
2/ Release ag-parent 0.2.1 to Central, using 0.2.0 of ag-misc
=> aligns minor version with ag-misc
=> Optionally: Adds checkstyle to pluginMngmt (AEROGEAR-358) (I can send a
PR)
No deletes needed. Maven world will not collapse ;-)
Karel
On Fri, 9 May 2014 12:21:15 +0200
Matthias Wessendorf <
mwessendorf@
> wrote:
> Hi,
>
> Andrea reported that the 0.1.2 release (see [1]) contains the wrong
> version
> number (0.2.0).
> This artifact was already pushed to maven central.
>
> On IRC we had the following idea:
> * update master to 0.1.2-SNAPSHOT
> * perform the release again (that hopefully will result in 0.1.2 on maven
> central)
>
> That still means we have a 0.2.0 on maven central. I will ask my contacts
> at Sonatype to remove the 0.2.0 bits;
>
> If folks are OK w/ that, I am happy to perform these steps by Monday
> morning
>
> Greetings,
> Matthias
>
> [1] https://github.com/aerogear/aerogear-misc/blob/0.1.2/pom.xml
>
_______________________________________________
aerogear-dev mailing list
aerogear-dev@.jboss
--
View this message in context:
http://aerogear-dev.1069024.n5.nabble.com/aerogear-dev-aerogear-misc-rele...
Sent from the aerogear-dev mailing list archive at Nabble.com.
6:36 p.m.
On Fri, 9 May 2014 08:45:35 -0700 (PDT)
Andrea Vibelli <avibelli(a)redhat.com> wrote:
Great that we agree on 1), which is the most important.
@Karel: what change would you require about checkstyle plugin (just
wondering)?
Right, I've realized that it is already there after posting. Thanks Andrea!
Karel Piwko wrote
> What about:
>
> 1/ Release ag-misc 0.1.2 to Central to fix ag-parent
> 2/ Release ag-parent 0.2.1 to Central, using 0.2.0 of ag-misc
> => aligns minor version with ag-misc
> => Optionally: Adds checkstyle to pluginMngmt (AEROGEAR-358) (I can send a
> PR)
>
> No deletes needed. Maven world will not collapse ;-)
>
> Karel
>
>
> On Fri, 9 May 2014 12:21:15 +0200
> Matthias Wessendorf <
> mwessendorf@
> > wrote:
>
>> Hi,
>>
>> Andrea reported that the 0.1.2 release (see [1]) contains the wrong
>> version
>> number (0.2.0).
>> This artifact was already pushed to maven central.
>>
>> On IRC we had the following idea:
>> * update master to 0.1.2-SNAPSHOT
>> * perform the release again (that hopefully will result in 0.1.2 on maven
>> central)
>>
>> That still means we have a 0.2.0 on maven central. I will ask my contacts
>> at Sonatype to remove the 0.2.0 bits;
>>
>> If folks are OK w/ that, I am happy to perform these steps by Monday
>> morning
>>
>> Greetings,
>> Matthias
>>
>> [1] https://github.com/aerogear/aerogear-misc/blob/0.1.2/pom.xml
>>
>
> _______________________________________________
> aerogear-dev mailing list
> aerogear-dev@.jboss
> https://lists.jboss.org/mailman/listinfo/aerogear-dev
--
View this message in context:
http://aerogear-dev.1069024.n5.nabble.com/aerogear-dev-aerogear-misc-rele...
Sent from the aerogear-dev mailing list archive at Nabble.com.
_______________________________________________ aerogear-dev mailing list
aerogear-dev(a)lists.jboss.org
https://lists.jboss.org/mailman/listinfo/aerogear-dev
2:49 p.m.
And I still can't see what's wrong....
On 2014-05-09, Karel Piwko wrote:
What about:
1/ Release ag-misc 0.1.2 to Central to fix ag-parent
2/ Release ag-parent 0.2.1 to Central, using 0.2.0 of ag-misc
=> aligns minor version with ag-misc
=> Optionally: Adds checkstyle to pluginMngmt (AEROGEAR-358) (I can send a PR)
No deletes needed. Maven world will not collapse ;-)
Karel
On Fri, 9 May 2014 12:21:15 +0200
Matthias Wessendorf <mwessendorf(a)gmail.com> wrote:
> Hi,
>
> Andrea reported that the 0.1.2 release (see [1]) contains the wrong version
> number (0.2.0).
> This artifact was already pushed to maven central.
>
> On IRC we had the following idea:
> * update master to 0.1.2-SNAPSHOT
> * perform the release again (that hopefully will result in 0.1.2 on maven
> central)
>
> That still means we have a 0.2.0 on maven central. I will ask my contacts
> at Sonatype to remove the 0.2.0 bits;
>
> If folks are OK w/ that, I am happy to perform these steps by Monday morning
>
> Greetings,
> Matthias
>
> [1] https://github.com/aerogear/aerogear-misc/blob/0.1.2/pom.xml
>
_______________________________________________
aerogear-dev mailing list
aerogear-dev(a)lists.jboss.org
https://lists.jboss.org/mailman/listinfo/aerogear-dev
--
abstractj
3 p.m.
The 0.2.0 has the wrong tag:
http://search.maven.org/remotecontent?filepath=org/jboss/aerogear/aerogea...
and, I think more important, the related release of the -parent was going
against 0.1.2 (and not 0.2.0):
http://search.maven.org/remotecontent?filepath=org/jboss/aerogear/aerogea...
That was the reason we did the 0.1.2 _after_ the 0.2.0
Next release will be 0.2.1 and atm nothing is broken
Andrea might be able to provide a few more details
On Mon, May 19, 2014 at 2:49 PM, Bruno Oliveira <bruno(a)abstractj.org> wrote:
And I still can't see what's wrong....
On 2014-05-09, Karel Piwko wrote:
> What about:
>
> 1/ Release ag-misc 0.1.2 to Central to fix ag-parent
> 2/ Release ag-parent 0.2.1 to Central, using 0.2.0 of ag-misc
> => aligns minor version with ag-misc
> => Optionally: Adds checkstyle to pluginMngmt (AEROGEAR-358) (I can send
a PR)
>
> No deletes needed. Maven world will not collapse ;-)
>
> Karel
>
>
> On Fri, 9 May 2014 12:21:15 +0200
> Matthias Wessendorf <mwessendorf(a)gmail.com> wrote:
>
> > Hi,
> >
> > Andrea reported that the 0.1.2 release (see [1]) contains the wrong
version
> > number (0.2.0).
> > This artifact was already pushed to maven central.
> >
> > On IRC we had the following idea:
> > * update master to 0.1.2-SNAPSHOT
> > * perform the release again (that hopefully will result in 0.1.2 on
maven
> > central)
> >
> > That still means we have a 0.2.0 on maven central. I will ask my
contacts
> > at Sonatype to remove the 0.2.0 bits;
> >
> > If folks are OK w/ that, I am happy to perform these steps by Monday
morning
> >
> > Greetings,
> > Matthias
> >
> > [1] https://github.com/aerogear/aerogear-misc/blob/0.1.2/pom.xml
> >
>
> _______________________________________________
> aerogear-dev mailing list
> aerogear-dev(a)lists.jboss.org
> https://lists.jboss.org/mailman/listinfo/aerogear-dev
--
abstractj
_______________________________________________
aerogear-dev mailing list
aerogear-dev(a)lists.jboss.org
https://lists.jboss.org/mailman/listinfo/aerogear-dev
--
Matthias Wessendorf
blog: http://matthiaswessendorf.wordpress.com/
sessions: http://www.slideshare.net/mwessendorf
twitter: http://twitter.com/mwessendorf
2:49 p.m.
Good morning,
AeroGear Misc was staged here and the version was discussed as well,
please check this thread
(http://aerogear-dev.1069024.n5.nabble.com/Release-of-AeroGear-Parent-td77...).
I can't see what's wrong. Semantically the correct would be 0.2.0.
On 2014-05-09, Matthias Wessendorf wrote:
Hi,
Andrea reported that the 0.1.2 release (see [1]) contains the wrong version
number (0.2.0).
This artifact was already pushed to maven central.
On IRC we had the following idea:
* update master to 0.1.2-SNAPSHOT
* perform the release again (that hopefully will result in 0.1.2 on maven
central)
That still means we have a 0.2.0 on maven central. I will ask my contacts
at Sonatype to remove the 0.2.0 bits;
If folks are OK w/ that, I am happy to perform these steps by Monday morning
Greetings,
Matthias
[1] https://github.com/aerogear/aerogear-misc/blob/0.1.2/pom.xml
--
Matthias Wessendorf
blog: http://matthiaswessendorf.wordpress.com/
sessions: http://www.slideshare.net/mwessendorf
twitter: http://twitter.com/mwessendorf
_______________________________________________
aerogear-dev mailing list
aerogear-dev(a)lists.jboss.org
https://lists.jboss.org/mailman/listinfo/aerogear-dev
--
abstractj
3:09 p.m.
The problem was that version of aerogear-misc - 0.1.2 - defined in
aerogear-parent was missing on Maven Central, there was just 0.2.0.
As dependencies in <dependencyManagement> are not checked for availability
during install phase, users trying to use aerogear-misc managed by
aerogear-parent will see a resolution failure.
This was fixed by releasing aerogear-misc 0.1.2, content equal to 0.2.0, to
Maven Central.
Karel
On Mon, 19 May 2014 09:49:10 -0300
Bruno Oliveira <bruno(a)abstractj.org> wrote:
Good morning,
AeroGear Misc was staged here and the version was discussed as well,
please check this thread
(http://aerogear-dev.1069024.n5.nabble.com/Release-of-AeroGear-Parent-td77...).
I can't see what's wrong. Semantically the correct would be 0.2.0.
On 2014-05-09, Matthias Wessendorf wrote:
> Hi,
>
> Andrea reported that the 0.1.2 release (see [1]) contains the wrong version
> number (0.2.0).
> This artifact was already pushed to maven central.
>
> On IRC we had the following idea:
> * update master to 0.1.2-SNAPSHOT
> * perform the release again (that hopefully will result in 0.1.2 on maven
> central)
>
> That still means we have a 0.2.0 on maven central. I will ask my contacts
> at Sonatype to remove the 0.2.0 bits;
>
> If folks are OK w/ that, I am happy to perform these steps by Monday morning
>
> Greetings,
> Matthias
>
> [1] https://github.com/aerogear/aerogear-misc/blob/0.1.2/pom.xml
>
> --
> Matthias Wessendorf
>
> blog: http://matthiaswessendorf.wordpress.com/
> sessions: http://www.slideshare.net/mwessendorf
> twitter: http://twitter.com/mwessendorf
> _______________________________________________
> aerogear-dev mailing list
> aerogear-dev(a)lists.jboss.org
> https://lists.jboss.org/mailman/listinfo/aerogear-dev
--
abstractj
_______________________________________________
aerogear-dev mailing list
aerogear-dev(a)lists.jboss.org
https://lists.jboss.org/mailman/listinfo/aerogear-dev
3623
days inactive
3633
days old
9 comments
6 participants
participants (6)
-
Andrea Vibelli -
Bruno Oliveira -
Daniel Bevenius -
Karel Piwko -
Matthias Wessendorf -
Matthias Wessendorf