Hi,
> Sure, I'll create a job and deploy it. I'll let you know if there
> are any problems.
What about my Axistools connector?
https://github.com/theit/m2e-lifecycle-axistools
I followed all the discussions recently, but I'm not sure if there's I
need to do...?
Apart from that, thanks for all
I will take a look at your build and I may need to adjust it. I use your build
and Benson's as a starting point for trying to document how the build should be
structured. I deploy whole p2 sites to Nexus which I don't believe many do
because it's a feature set in Nexus Pro that I'm open sourcing
Jason,
What's your model of 'releases' for plugins connected to your
structure? How does someone who works on the plugin trigger the
process on your end?
--benson
___
m2e-users mailing list
m2e-users@eclipse.org
https://dev.eclipse.org/mailman/listinfo/
It's continuous delivery. Builds happen via CI, they get deployed to Nexus and
you pick the one you deem release worthy to go into the catalog by making a
pull request to change the catalog. It will get more sophisticated but this is
what it is for now. I will change the triggers so that a build
On Mon, Oct 8, 2012 at 10:51 AM, Jason van Zyl wrote:
> It's continuous delivery. Builds happen via CI, they get deployed to Nexus
> and you pick the one you deem release worthy to go into the catalog by
> making a pull request to change the catalog. It will get more sophisticated
> but this is wh
On Mon, Oct 8, 2012 at 10:51 AM, Jason van Zyl wrote:
> It's continuous delivery. Builds happen via CI, they get deployed to Nexus
> and you pick the one you deem release worthy to go into the catalog by
> making a pull request to change the catalog. It will get more sophisticated
> but this is wh
I just tried to import some projects into a fresh Eclipse into which I had
just installed m2e 1.2 and it appears to continue to want to go to
http://repository.tesla.io:8081/nexus/, which due to corporate firewall
stuff is not reachable:
Problems occurred while performing installation: Error(s) oc
On Mon, Oct 8, 2012 at 10:58 AM, Benson Margulies wrote:
> On Mon, Oct 8, 2012 at 10:51 AM, Jason van Zyl wrote:
>> It's continuous delivery. Builds happen via CI, they get deployed to Nexus
>> and you pick the one you deem release worthy to go into the catalog by
>> making a pull request to chan
EdgeCast does cache things, the new catalog is up there. I'll try to purge the
cache.
On Oct 8, 2012, at 11:04 AM, Nathaniel Mishkin wrote:
> I just tried to import some projects into a fresh Eclipse into which I had
> just installed m2e 1.2 and it appears to continue to want to go to
> http:
To help validate that the right catalog and contents are making it to Central
along with the catalog JARs I have deployed the connectors.xml file that is
used to generate the content for the update manager:
http://repo1.maven.org/maven2/.m2e/discovery-catalog/
Specifically you will see that the
10 matches
Mail list logo
