No problem.
On 9/21/2015 12:54 PM, Stian Soiland-Reyes wrote:
Right. Are you OK to have a go updating them and checking if Jenkins
is happy again?
I think we should add a section about this in the release procedure.
https://github.com/apache/incubator-taverna-site/blob/trunk/content/community/releasing.md
On 21 September 2015 at 07:12, Dmitry <[email protected]> wrote:
I guess the artifactory Maven server flushed old SNAPSHOTS.. as it
probably should.
Exactly. Jenkins fails to rebuild:
The parent is defined
https://github.com/apache/incubator-taverna-maven-parent/blob/master/pom.xml
(2-incubating-SNAPSHOT)
while modules, for instance:
https://github.com/apache/incubator-taverna-common-activities/blob/master/pom.xml
are looking for the 1-incubating-SNAPSHOT.
On 9/21/2015 2:57 AM, Stian Soiland-Reyes wrote:
I guess the artifactory Maven server flushed old SNAPSHOTS.. as it
probably should.
I think they should be referring to the released parent 1-incubating,
unless there is a reason why you need 2-incubating-SNAPSHOT (e.g. you
have added another <property> or <plugin> there).
Otherwise it would look like you need a new parent release
2-incubating, even though nothing has changed.
On 16 September 2015 at 15:58, Dmitry <[email protected]> wrote:
Hello everybody,
I noticed that taverna has changed the parent to the
2-incubating-SNAPSHOT.
Some builds become broken saying they couldn't find 1-incubating-SNAPSHOT
Should we change all parents to 2-incubating-SNAPSHOT?
Cheers,
Dmitry
