Eclipse Community Forums: QVT-OML » ant qvto:transformation and "PackageNotFoundException"

Home » Modeling » QVT-OML » ant qvto:transformation and "PackageNotFoundException"

ant qvto:transformation and "PackageNotFoundException" [message #946826]

Tue, 16 October 2012 10:45

Eclipse User

DISCLAIMER:
You can only use links to eclipse.org sites while you have fewer than 25 messages. So, I remove any links.

Hi there!

My qvto transformation works fine through eclipse Run section.
But, if I migrated to use ant script:

<project name="project" default="default" xmlns:qvto="http://www.eclipse.org/qvt/1.0.0/Operational">
    <target name="default">
    	
        <qvto:transformation uri="../Mapping/transforms/One2Next.qvto">
            <in 
                uri="../Mapping/model/one.uml"
            />
            <in 
                uri="./Dictionary.xmi"
            />
            <out
                uri="./out/One_as_Next.xmi"
            />
        </qvto:transformation>
    </target>
</project>

it throws an well known exception:
Caused by: org.eclipse.emf.ecore.xmi.PackageNotFoundException: Package with uri 'parser sucks://schema_of_MyStandard_goes_here' not found.

I checked
Quote:

eclipsedriven.blogspot.com/2010/12/fixing-emfecorexmi-resource-loading.html

, but how can I register my package using ant script?

plugin.xml:

<plugin>

   <extension point="org.eclipse.emf.ecore.generated_package">
      <package
            uri="parser sucks://MyStandard_reference_goes_here"
            class="org.mypackage.MyStandardPackage"
            genModel="model/MyStandard.genmodel"/>
   </extension>

   <extension point="org.eclipse.emf.ecore.extension_parser">
      <parser
            type="mystandard"
            class="org.mypackage.util.MyStandardResourceFactoryImpl"/>
   </extension>

</plugin>

Re: ant qvto:transformation and "PackageNotFoundException" [message #946905 is a reply to message #946826]

Tue, 16 October 2012 12:09

Eclipse User

Hi

I have never used the ant script so cannit offer any experience-based
advice.

Your examples are full of suspicious content; it is not clear how much
is due to working artound newsgroup link postring limitations and how
much from unhelpful names.

I'm afraid that I will not be able to give you any further help without
a zipped project including a launch configuration that can just be
installed and run to demonstrate your problem.

Regards

Ed Willink

On 16/10/2012 15:45, Alexander Unsonamed wrote:
> DISCLAIMER:
> You can only use links to eclipse.org sites while you have fewer than
> 25 messages. So, I remove any links.
>
>
> Hi there!
>
> My qvto transformation works fine through eclipse Run section.
> But, if I migrated to use ant script:
>
> <project name="project" default="default"
> xmlns:qvto="http://www.eclipse.org/qvt/1.0.0/Operational">
> <target name="default">
>
> <qvto:transformation uri="../Mapping/transforms/One2Next.qvto">
> <in uri="../Mapping/model/one.uml"
> />
> <in uri="./Dictionary.xmi"
> />
> <out
> uri="./out/One_as_Next.xmi"
> />
> </qvto:transformation>
> </target>
> </project>
>
> it throws an well known exception:
> Caused by: org.eclipse.emf.ecore.xmi.PackageNotFoundException: Package
> with uri 'parser sucks://schema_of_MyStandard_goes_here' not found.
>
> I checked Quote:
>> eclipsedriven.blogspot.com/2010/12/fixing-emfecorexmi-resource-loading.html
>>
> , but how can I register my package using ant script?
>
> plugin.xml:
>
> <plugin>
>
> <extension point="org.eclipse.emf.ecore.generated_package">
> <package
> uri="parser sucks://MyStandard_reference_goes_here"
> class="org.mypackage.MyStandardPackage"
> genModel="model/MyStandard.genmodel"/>
> </extension>
>
> <extension point="org.eclipse.emf.ecore.extension_parser">
> <parser
> type="mystandard"
> class="org.mypackage.util.MyStandardResourceFactoryImpl"/>
> </extension>
>
> </plugin>
>

Previous Topic:	[QVTo] trace model and proxies
Next Topic:	Operational QVT Interpreter

Goto Forum:

-=] Back to Top [=-

Current Time: Sun Jul 06 07:54:58 EDT 2025

.:: Contact :: Home ::.

Breadcrumbs

Sign up to our Newsletter