You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@tapestry.apache.org by Howard Lewis Ship <hl...@gmail.com> on 2015/02/03 01:48:42 UTC
Watcha make of this?
Something in the build recently changed, I think:
$ gradle genR -x test
...
:quickstart:clean
:quickstart:uploadPublished FAILED
FAILURE: Build failed with an exception.
* What went wrong:
Execution failed for task ':quickstart:uploadPublished'.
> Could not publish configuration 'published'
> Cannot publish artifact 'quickstart.jar
(org.apache.tapestry:quickstart:5.4-beta-27)'
(/Users/hlship/workspaces/tapestry/tapestry5/quickstart/build/libs/quickstart-5.4-beta-27.jar)
as it does not exist.
* Try:
Run with --stacktrace option to get the stack trace. Run with --info or
--debug option to get more log output.
BUILD FAILED
Total time: 2 mins 18.358 secs
~/workspaces/t5
I have to leave for the day, but I'd like to generate the next beta. Any
insight into what might have changed would be appreciated.
--
Howard M. Lewis Ship
Creator of Apache Tapestry
The source for Tapestry training, mentoring and support. Contact me to
learn how I can get you up and productive in Tapestry fast!
(971) 678-5210
http://howardlewisship.com
@hlship
Re: Watcha make of this?
Posted by Jochen Kemnade <ke...@gmail.com>.
I'm still trying to understand why the current task dependencies are the
way they are.
Am 03.02.2015 um 18:55 schrieb Jochen Kemnade:
> why does generateRelease depend on continuousIntegration?
I think it shouldn't be like that and I'll try to remove that
dependency. Those tasks are not related anymore. And even with the old
non-SVN deployment procedure, the dependency should have been the other
way around IMHO. Or am I missing something?
> And why do we need to do quickstart:clean at all?
This dates way back to 2011-10-26:
commit db4b4aa3e997ea6ca9503dfa7f4c65f10445ebc9
Author: Howard Lewis Ship <hl...@apache.org>
Date: Wed Oct 26 17:47:14 2011 +0000
TAP5-1728: Quickstart archetype does not include the build.gradle
I wonder if that's still necessary.
On my machine, I removed the dependency from generateRelease on
"quickstart:clean" and continuousIntegration (patch attached) and
created a fake -beta-28 release and the build.gradle and pom.xml in the
quickstart jar looked fine.
I'd say we try it that way. Howard, what do you think? Or anyone else?
Jochen
Re: Watcha make of this?
Posted by Jochen Kemnade <ke...@gmail.com>.
Am 03.02.2015 um 16:16 schrieb Howard Lewis Ship:
> I've temporarily reverted 15a0276584a529a5e4b08e6c90450936d000eec9
My change made Gradle run the quickstart:clean task directly before the
quickstart:uploadArchives task:
task generateRelease {
dependsOn "quickstart:clean", continuousIntegration,
subprojects.uploadPublished, copyArchives
...
}
So first, it creates the artifacts and signs them, then, they are
removed by the clean task and then they are gone for the uploadPublished
task.
I think we'll need to have a look at those task dependencies, there
might be some tweaking to do, e.g. why does generateRelease depend on
continuousIntegration? And why do we need to do quickstart:clean at all?
I'm quite sick right now and it's over my head, but I can have a look in
a day or two.
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@tapestry.apache.org
For additional commands, e-mail: dev-help@tapestry.apache.org
Re: Watcha make of this?
Posted by Howard Lewis Ship <hl...@gmail.com>.
I've temporarily reverted 15a0276584a529a5e4b08e6c90450936d000eec9.
On Mon, Feb 2, 2015 at 11:57 PM, Jochen Kemnade <jo...@eddyson.de>
wrote:
> Am 03.02.2015 um 01:48 schrieb Howard Lewis Ship:
>
>> I have to leave for the day, but I'd like to generate the next beta. Any
>> insight into what might have changed would be appreciated.
>>
>
> That was probably me:
>
> commit 15a0276584a529a5e4b08e6c90450936d000eec9
> Author: Jochen Kemnade <jo...@eddyson.de>
> Date: Tue Jan 20 09:41:53 2015 +0100
>
> don't have Jenkins upload the generated artifacts. Currently, this is
> not adapted to the new SVN based upload process and causes the CI builds to
> fail.
>
> diff --git a/build.gradle b/build.gradle
> index 45dbcc2..6b47623 100755
> --- a/build.gradle
> +++ b/build.gradle
> @@ -398,7 +398,7 @@ dependencies {
> }
>
> task continuousIntegration {
> - dependsOn subprojects.build, aggregateJavadoc,
> subprojects.uploadPublished
> + dependsOn subprojects.build, aggregateJavadoc
> description "Task executed on Jenkins CI server after SVN commits"
> }
>
> But I don't understand why that would cause missing artifacts. As the
> generateReleaseTask depends on subprojects.uploadPublished as well, that
> should not have changed anything.
> I'll have a look when I get home from work.
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: dev-unsubscribe@tapestry.apache.org
> For additional commands, e-mail: dev-help@tapestry.apache.org
>
>
--
Howard M. Lewis Ship
Creator of Apache Tapestry
The source for Tapestry training, mentoring and support. Contact me to
learn how I can get you up and productive in Tapestry fast!
(971) 678-5210
http://howardlewisship.com
@hlship
Re: Watcha make of this?
Posted by Jochen Kemnade <jo...@eddyson.de>.
Am 03.02.2015 um 01:48 schrieb Howard Lewis Ship:
> I have to leave for the day, but I'd like to generate the next beta. Any
> insight into what might have changed would be appreciated.
That was probably me:
commit 15a0276584a529a5e4b08e6c90450936d000eec9
Author: Jochen Kemnade <jo...@eddyson.de>
Date: Tue Jan 20 09:41:53 2015 +0100
don't have Jenkins upload the generated artifacts. Currently, this
is not adapted to the new SVN based upload process and causes the CI
builds to fail.
diff --git a/build.gradle b/build.gradle
index 45dbcc2..6b47623 100755
--- a/build.gradle
+++ b/build.gradle
@@ -398,7 +398,7 @@ dependencies {
}
task continuousIntegration {
- dependsOn subprojects.build, aggregateJavadoc,
subprojects.uploadPublished
+ dependsOn subprojects.build, aggregateJavadoc
description "Task executed on Jenkins CI server after SVN commits"
}
But I don't understand why that would cause missing artifacts. As the
generateReleaseTask depends on subprojects.uploadPublished as well, that
should not have changed anything.
I'll have a look when I get home from work.
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@tapestry.apache.org
For additional commands, e-mail: dev-help@tapestry.apache.org