You'll need remove & reimport project whenever you add a new module or
move a module to different place...
It would be a little more usable if the folder hiding hack could be
reapplied to an existing project during Update Configuration action.
I have no idea if it's feasible, and sadly I don't ha
Igor, has this issue been raised to the Platform group at all? I am curious
if this is already on your roadmap. I can create a ticket but I don't know
how much traction it will get.
Paul
On Tue, Oct 2, 2012 at 10:12 AM, Igor Fedorenko wrote:
> This is Eclipse workspace limitation and needs to b
I have published the catalog to Maven Central.
On Oct 1, 2012, at 10:40 AM, Anders Hammar wrote:
> Just to stress the importance of getting this out as soon as possible,
> have a look at the two questions on this mailing list just today
> related to invalid connectors in the currently published
Just checked the plugin.xml in the 1.1 jar and it doesn't look
correct. It lists connector versions which aren't compatible with m2e
1.2.
/Anders
On Wed, Oct 3, 2012 at 8:04 PM, Jason van Zyl wrote:
> I have published the catalog to Maven Central.
>
> On Oct 1, 2012, at 10:40 AM, Anders Hammar
It's the same as the staging catalog. So what you're saying is no one really
looked at the staging catalog :-)
On Oct 3, 2012, at 12:51 PM, Anders Hammar wrote:
> Just checked the plugin.xml in the 1.1 jar and it doesn't look
> correct. It lists connector versions which aren't compatible with m
No, there's really something fishy about the released catalog. The staged
discovery catalog points at
http://repository.tesla.io:8081/nexus/content/sites/m2e.discovery.stage/org.eclipse.m2e.discovery.oss-catalog-1.1.jar
which content is different from
http://repo1.maven.org/maven2/.m2e/discovery-
I just republished the production catalog again, it should be identical to the
staging catalog.
On Oct 3, 2012, at 4:02 PM, Eric Dalquist wrote:
> I'm using the staging category (since it actually works with 1.2) via the
> instructions on https://github.com/tesla/m2e-discovery-catalog and have
Fixed. The name of the JAR doesn't change so EdgeCast wasn't pulling from the
source. Should be fixed now, I just tried it and the right metadata is being
pulled.
On Oct 3, 2012, at 3:15 PM, Fred Bricon wrote:
> No, there's really something fishy about the released catalog. The staged
> disco
Yes, there are existing requests already, 35973 and 245412, for example.
Given that one of these requests was opened back in 2003 and the other
in 2008, I highly doubt anything will ever happen to improve nested
project support in Eclipse.
https://bugs.eclipse.org/bugs/show_bug.cgi?id=35973
https
Thanks, looks much better!
/Anders
On Thu, Oct 4, 2012 at 4:09 AM, Jason van Zyl wrote:
> Fixed. The name of the JAR doesn't change so EdgeCast wasn't pulling from
> the source. Should be fixed now, I just tried it and the right metadata is
> being pulled.
>
> On Oct 3, 2012, at 3:15 PM, Fred Br
10 matches
Mail list logo
