Skip to main content
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index] [List Home]
Re: [virgo-dev] Reactivation of Virgo Snaps project

Hi GianMaria, Dani,

thank you very much for your guidance - that sounds reasonable.

Cheers,
Stefan


On 2016-11-04 15:41, Giamma wrote:

I believe Glyn used to mark such bugs as "help wanted", then contributors would add a comment declaring that they would take ownership of it.

GianMaria.


Il Ven 4 Nov 2016, 13:03 dmarthaler@xxxxxxx <dmarthaler@xxxxxxx> ha scritto:

Well, for non-commiters it is currently not possible to assign a bug.
Usually I assign the bugs to myself which I'm currently working on. And I think the others are doing the same. So, as long as a bug is not assigned to anyone you can work on it.

Maybe Florian has an idea how to reflect this in Bugzilla?

Regards,
Dani

On 11/03/2016 09:35 PM, Stefan Zugal wrote:

Hi Dani,

thank you very much for your effort - I really appreciate that!

Following your instructions, I have checked out the project, built the Snaps and installed them locally on a recent server (3.7.0.M03). Everything went well and the snap bundles start properly.

I was wondering whether you have a way saying "I am now working on this bug" - similar to "accepting" a ticket?

Cheers,
Stefan


On 2016-11-03 10:01, dmarthaler@xxxxxxx wrote:

Dear all

I have invested some time to move the Virgo Snaps project from Ant/Ivy to Gradle build [1]. I pushed those changes to a new branch (development) into the repository [2]. The build now allows to build Snaps using the following options on the command line:

./gradlew clean build snapsDist -x :org.eclipse.virgo.snaps.test:test

Currently the 'test' task of the 'org.eclipse.virgo.snaps.test' sub project must be excluded as I was not able to get it to work until now. Anyway, it relies upon the Virgo test framework which we want to replace with PaxExam as I understood from previous conversation on virgo-dev. So, maybe we could directly move those integration tests using PaxExam instead of getting it to work with the old Virgo test framework.

I also created a Hudson job for building Virgo Snaps from development branch [3].

The project can now be imported using Gradles Buildship plugin in Eclipse/STS. I will additionally add Markdown Documentation files to the project later this week.

@Stefan Zugal: If you're still up to this you can checkout the project 'git clone git://git.eclipse.org/gitroot/virgo/org.eclipse.virgo.snaps.git --recursive' and give it a try. Let me know if you face some issues. If importing to your IDE works as expected please test it using one of the latest builds of Virgo for Tomcat server and let us know if it works or not.

Regards,
Dani

[1] https://bugs.eclipse.org/bugs/show_bug.cgi?id=506579
[2] http://git.eclipse.org/c/virgo/org.eclipse.virgo.snaps.git/commit/?h=development&id=9a5bdea3eae1ef38c591b00e1096d490ecb70858
[3] https://hudson.eclipse.org/virgo/view/Snaps/job/Snaps-Development/



_______________________________________________
virgo-dev mailing list
virgo-dev@xxxxxxxxxxx
To change your delivery options, retrieve your password, or unsubscribe from this list, visit
https://dev.eclipse.org/mailman/listinfo/virgo-dev



_______________________________________________
virgo-dev mailing list
virgo-dev@xxxxxxxxxxx
To change your delivery options, retrieve your password, or unsubscribe from this list, visit
https://dev.eclipse.org/mailman/listinfo/virgo-dev

_______________________________________________
virgo-dev mailing list
virgo-dev@xxxxxxxxxxx
To change your delivery options, retrieve your password, or unsubscribe from this list, visit
https://dev.eclipse.org/mailman/listinfo/virgo-dev


_______________________________________________
virgo-dev mailing list
virgo-dev@xxxxxxxxxxx
To change your delivery options, retrieve your password, or unsubscribe from this list, visit
https://dev.eclipse.org/mailman/listinfo/virgo-dev

Back to the top