photran-dev http://dev.eclipse.org/mhonarc/lists/photran-dev/maillist.html photran-dev en-us Mon, 09 Nov 2009 20:10:04 GMT Mon, 09 Nov 2009 20:10:04 GMT http://blogs.law.harvard.edu/tech/rss MHonArc RSS 2.0 RCFile webmaster@eclipse.org (Webmaster) webmaster@eclipse.org (Webmaster) photran-dev http://www.eclipse.org/eclipse.org-common/themes/Phoenix/images/eclipse_home_header.jpg http://dev.eclipse.org/mhonarc/lists/photran-dev/maillist.html Re: [photran-dev] major problem with plugin names http://dev.eclipse.org/mhonarc/lists/photran-dev/msg00345.html Yes, exactly. You're right that it makes sense to package it separately and set up a dependency at install time. I'll take care of that as soon as I can. Jeff Is it your intention that these plugins would be completely separate feature that can be used by other projects?
Yes, exactly. You're right that it makes sense to package it separately and set up a dependency at install time. I'll take care of that as soon as I can.

Jeff

]]> Mon, 09 Nov 2009 20:01:05 GMT http://dev.eclipse.org/mhonarc/lists/photran-dev/msg00345.html subscribe-photran-dev@xxxxxxx (Jeffrey Overbey) Re: [photran-dev] major problem with plugin names http://dev.eclipse.org/mhonarc/lists/photran-dev/msg00344.html Wait, none of the Photran projects have "ptp" in the names, since we moved them from the Technology CVS repo. There's no way we're going to rename all of them. If we were going to do that, it should have happened when we did the merge several months ago. T... Jeff,
Is it your intention that these plugins would be completely separate feature that can be used by other projects? If so, then keeping the existing name might be feasible. You'll need to provide a feature project that packages them separately, and they'll need to be available as a separate download from the update site.

Greg

On Nov 6, 2009, at 4:30 PM, Jeffrey Overbey wrote:

It's even more confusing not to have ptp in the plugin name, and it's

Wait, none of the Photran projects have "ptp" in the names, since we moved them from the Technology CVS repo. There's no way we're going to rename all of them. If we were going to do that, it should have happened when we did the merge several months ago.

the plugins are identifiable with the project they are from

The Rephraser plug-ins all have "Eclipse.org - Photran" as the provider. I can change it to "Eclipse.org - PTP/Photran" or something if we need to mention PTP. At any rate, this makes it obvious what project they're from.

Jeff
_______________________________________________
photran-dev mailing list
photran-dev@xxxxxxxxxxx
https://dev.eclipse.org/mailman/listinfo/photran-dev


]]> Fri, 06 Nov 2009 22:07:54 GMT http://dev.eclipse.org/mhonarc/lists/photran-dev/msg00344.html g.watson@xxxxxxx (Greg Watson) Re: [photran-dev] major problem with plugin names http://dev.eclipse.org/mhonarc/lists/photran-dev/msg00343.html Wait, none of the Photran projects have &quot;ptp&quot; in the names, since we moved them from the Technology CVS repo. There's no way we're going to rename all of them. If we were going to do that, it should have happened when we did the merge several months ago. T... The naming convention is generally org.eclipse.<project>. I realize other projects have not always followed this convention, but I think it's incorrect IMHO as it pollutes the namespace. The photran plugins are only the way they are because they started life as a separate project. If it doesn't make sense for them to be named under the photran (sub-)project, then they should be named under the parent project, ptp.

Greg

On Nov 6, 2009, at 4:30 PM, Jeffrey Overbey wrote:

It's even more confusing not to have ptp in the plugin name, and it's

Wait, none of the Photran projects have "ptp" in the names, since we moved them from the Technology CVS repo. There's no way we're going to rename all of them. If we were going to do that, it should have happened when we did the merge several months ago.

the plugins are identifiable with the project they are from

The Rephraser plug-ins all have "Eclipse.org - Photran" as the provider. I can change it to "Eclipse.org - PTP/Photran" or something if we need to mention PTP. At any rate, this makes it obvious what project they're from.

Jeff
_______________________________________________
photran-dev mailing list
photran-dev@xxxxxxxxxxx
https://dev.eclipse.org/mailman/listinfo/photran-dev


]]> Fri, 06 Nov 2009 21:52:29 GMT http://dev.eclipse.org/mhonarc/lists/photran-dev/msg00343.html g.watson@xxxxxxx (Greg Watson) Re: [photran-dev] major problem with plugin names http://dev.eclipse.org/mhonarc/lists/photran-dev/msg00342.html Wait, none of the Photran projects have &quot;ptp&quot; in the names, since we moved them from the Technology CVS repo. There's no way we're going to rename all of them. If we were going to do that, it should have happened when we did the merge several months ago. T... It's even more confusing not to have ptp in the plugin name, and it's
Wait, none of the Photran projects have "ptp" in the names, since we moved them from the Technology CVS repo. There's no way we're going to rename all of them. If we were going to do that, it should have happened when we did the merge several months ago.

the plugins are identifiable with the project they are from

The Rephraser plug-ins all have "Eclipse.org - Photran" as the provider. I can change it to "Eclipse.org - PTP/Photran" or something if we need to mention PTP. At any rate, this makes it obvious what project they're from.

Jeff

]]> Fri, 06 Nov 2009 21:30:25 GMT http://dev.eclipse.org/mhonarc/lists/photran-dev/msg00342.html subscribe-photran-dev@xxxxxxx (Jeffrey Overbey) Re: [photran-dev] major problem with plugin names http://dev.eclipse.org/mhonarc/lists/photran-dev/msg00341.html I purposely left &quot;photran&quot; out of the project names because those projects contain the language-independent parts of the refactoring engine -- Photran (and some other refactoring tools we're working on) depend on them, not the other way around. It's going ... It's even more confusing not to have ptp in the plugin name, and it's important that the plugins are identifiable with the project they are from. If you want to use something like org.eclipse.ptp.lang.rephraserengine then I'm fine with that.

Greg


On Nov 6, 2009, at 3:29 PM, Jeffrey Overbey wrote:

I've just noticed that the rephraserengine plugin names are all

I purposely left "photran" out of the project names because those projects contain the language-independent parts of the refactoring engine -- Photran (and some other refactoring tools we're working on) depend on them, not the other way around. It's going to be tremendously confusing if we have org.eclipse.photran.core.vpg and org.eclipse.photran.rephraserengine.core.vpg and so on, where the first one contains Fortran-specific stuff and the second one doesn't. They are attributed to Photran in the manifests. There seems to be precedent for this, browsing through Eclipse CVS...

Jeff
_______________________________________________
photran-dev mailing list
photran-dev@xxxxxxxxxxx
https://dev.eclipse.org/mailman/listinfo/photran-dev


]]> Fri, 06 Nov 2009 21:09:13 GMT http://dev.eclipse.org/mhonarc/lists/photran-dev/msg00341.html g.watson@xxxxxxx (Greg Watson) Re: [photran-dev] major problem with plugin names http://dev.eclipse.org/mhonarc/lists/photran-dev/msg00340.html I purposely left &quot;photran&quot; out of the project names because those projects contain the language-independent parts of the refactoring engine -- Photran (and some other refactoring tools we're working on) depend on them, not the other way around. It's going ... I've just noticed that the rephraserengine plugin names are all
I purposely left "photran" out of the project names because those projects contain the language-independent parts of the refactoring engine -- Photran (and some other refactoring tools we're working on) depend on them, not the other way around. It's going to be tremendously confusing if we have org.eclipse.photran.core.vpg and org.eclipse.photran.rephraserengine.core.vpg and so on, where the first one contains Fortran-specific stuff and the second one doesn't. They are attributed to Photran in the manifests. There seems to be precedent for this, browsing through Eclipse CVS...

Jeff

]]> Fri, 06 Nov 2009 20:29:16 GMT http://dev.eclipse.org/mhonarc/lists/photran-dev/msg00340.html subscribe-photran-dev@xxxxxxx (Jeffrey Overbey) [photran-dev] major problem with plugin names http://dev.eclipse.org/mhonarc/lists/photran-dev/msg00339.html I've just noticed that the rephraserengine plugin names are all incorrect. They are org.eclipse.rephraserengine rather than org.eclipse.ptp.photran.rephraserengine. These need to be fixed asap, preferably today. Greg I've just noticed that the rephraserengine plugin names are all incorrect. They are org.eclipse.rephraserengine rather than org.eclipse.ptp.photran.rephraserengine.

These need to be fixed asap, preferably today.

Greg

]]> Fri, 06 Nov 2009 18:33:20 GMT http://dev.eclipse.org/mhonarc/lists/photran-dev/msg00339.html g.watson@xxxxxxx (Greg Watson) [photran-dev] Project meta data is out of date for tools.ptp.photran http://dev.eclipse.org/mhonarc/lists/photran-dev/msg00338.html Jeffrey, Ralph, Projects are required to keep meta data up to date using the MyFoundation Portal (http://portal.eclipse.org/). The following problems were found with this project's meta-data: * The date for release &quot;5.0&quot; is in the past, but the release is ... Jeffrey, Ralph, Projects are required to keep meta data up to date using the MyFoundation Portal (http://portal.eclipse.org/). The following problems were found with this project's meta-data: * The date for release "5.0" is in the past, but the release is not marked as completed. If it is completed, it should be marked as completed; if it has been postponed, it should be given a new target date. * There is no next/future release of this project. All Eclipse projects must have a "next release" planned and scheduled. * There is no 'projecturl' pointing to the project home page ]]> Thu, 05 Nov 2009 05:00:12 GMT http://dev.eclipse.org/mhonarc/lists/photran-dev/msg00338.html emo@xxxxxxx (portal on behalf of emo) [photran-dev] Some packages renamed/classes moved http://dev.eclipse.org/mhonarc/lists/photran-dev/msg00337.html Since Photran's 5.0 release is coming up at the end of the month, I had to add &quot;internal&quot; to some package names to make it clear that they are not part of any published API. If you have local changes and updating from CVS breaks your code, just click Sourc... Since Photran's 5.0 release is coming up at the end of the month, I had to add "internal" to some package names to make it clear that they are not part of any published API.

If you have local changes and updating from CVS breaks your code, just click Source > Organize Imports. No classes have changed; they're probably just in a package with a different name.

Jeff

]]> Tue, 03 Nov 2009 16:32:18 GMT http://dev.eclipse.org/mhonarc/lists/photran-dev/msg00337.html subscribe-photran-dev@xxxxxxx (Jeffrey Overbey) Re: [photran-dev] Trying to build old versions http://dev.eclipse.org/mhonarc/lists/photran-dev/msg00336.html Is there a build.xml or similar floating around for building these? Unfortunately, no. This was code that we wrote and then never really touched again.

The situation is much better in HEAD (the stuff that was in those JARs is now in the Rephraser projects), but that doesn't really help you if you're trying to build an old version.

Jeff


Orion Poplawski wrote:
On 11/02/2009 12:40 PM, Jeffrey Overbey wrote: 
Um... it should be packaged into the JAR itself, and the JAR should be
on the classpath for the relevant projects.

Jeff


Orion Poplawski wrote: 
Okay, think I've found my issue - where is the source for
cdtdb-4.0.3-eclipse.jar and vpg-eclipse.jar?



Is there a build.xml or similar floating around for building these?


]]> Mon, 02 Nov 2009 20:55:09 GMT http://dev.eclipse.org/mhonarc/lists/photran-dev/msg00336.html subscribe-photran-dev@xxxxxxx (Jeffrey Overbey)